Live data from Hacker News

Atlassian acquires Trello for $425M

techcrunch.com

661–670 of 765 posts

Re: Atlassian acquires Trello for $425M

#661

This saddens me, and I suspect the future Trello will be a much different animal from what it is today. It could be better, but my gut says not.

It has been used extensively in our organization too, and our CTO is now searching replacements after the announcement.

We've have been exposed to JIRA through external suppliers and that has been enough to make him on his edges now.

Personally I don't think much will change, at least in the first year or so until the contracts of the original developers lapse and they can move on to new things.

Re: Atlassian acquires Trello for $425M

#662

Very happy for the folks at Trello. Great outcome for a great tool. Seems lots of JIRA-haters in the comments but lets get back and look at this event. The folks at Fog Creek brought us FogBugz, Stackoverflow, Trello. We should celebrate their success because its events like this that create the motivation for some of us to go create something that "stands on their shoulders" or competes with them or creates some new…

Hmm... How long does a company have to be around until it's no longer considered a start-up?

Re: Atlassian acquires Trello for $425M

#663
post #248

Earlier quoted context omitted.

Thats about all Atlassian is good at. HipChat has become an abomination of a client across Windows and Mac. Every new release is about fixing functionality they broke with the previous release and even then it still isn't fixed. Logging in from multiple places has always been terrible. I'll be logged in on Mac and available but randomly get emails as if I'm offline. I'll be online on my phone and get e-mails. I wan't…

And don't even get me started on SourceTree. Just about every release since 1.5.2 is a disaster, to the point of almost non-usable right now.

A Mac user said it should be quite good on OS X, but it sucks on Windows.

It is incredible slow for many operations.

My solution is to use command line git for most operations and SourceTree just for visualizing the repository. It's pretty fine for this.

Re: Atlassian acquires Trello for $425M

#664

Very happy for the folks at Trello. Great outcome for a great tool. Seems lots of JIRA-haters in the comments but lets get back and look at this event. The folks at Fog Creek brought us FogBugz, Stackoverflow, Trello. We should celebrate their success because its events like this that create the motivation for some of us to go create something that "stands on their shoulders" or competes with them or creates some new…

Hmm... How long does a company have to be around until it's no longer considered a start-up?

Plus Fog Creek is more on an anti-start-up since it explicitly did not want to grow fast at all costs. That's why Trello was spun off.

Re: Atlassian acquires Trello for $425M

#666

Earlier quoted context omitted.

Thanks for the detailed reply. The downtime issue is certainly understandable. I hope you're keeping customer data out of DVCS, but it's true that flaws in your code might be more "discoverable" if an attacker had that code. It does introduce another step into the attack, however, to have to hack FogBugz before reading your code and discovering the flaw that hacks your services. You know your threat model better than…

I'm not too concerned about someone getting the code, reading it and discovering a flaw allowing for exploit. I'm much more concerned about someone being able to modify code that will be pulled onto production systems by build and deployment scripts (not to mention the build and deployment scripts themselves) which would allow direct access without any need to hack anything beyond the external cloud service. Even a d…

Does anyone care enough about your product to actually go to the trouble to do that? It seems that in terms of actual risk management, managing an on premise version of everything is mitigation out of scale with the actual risk.

Besides, a disgruntled employee of your company is far more likely to be malicious than a disgruntled employee of some random cloud services company. What would be their motivation? They probably don't care about your code at all -- but your employees -- they certainly might. Has there ever been a case of a disgruntled Github employee hacking a customer company's production code ever in the history of Github? Has there ever in the history of SMEs been a disgruntled employee that harmed his own company? All the time.

So what risk is more realistic to mitigate? The hypothetical disgruntled employee at a vendor that probably has never heard of you or employees sitting right there in the office with you?

Re: Atlassian acquires Trello for $425M

#667

Really eager to hear what Spolsky has to say about the acquisition (nothing yet either on his blog or on Twitter).

His company is Stack Overflow, not Trello, so he probably doesn't have much to say.

Have a look at the history please. Trello came out of a company Joel created.

Re: Atlassian acquires Trello for $425M

#668

Very happy for the folks at Trello. Great outcome for a great tool. Seems lots of JIRA-haters in the comments but lets get back and look at this event. The folks at Fog Creek brought us FogBugz, Stackoverflow, Trello. We should celebrate their success because its events like this that create the motivation for some of us to go create something that "stands on their shoulders" or competes with them or creates some new…

Hmm... How long does a company have to be around until it's no longer considered a start-up?

I think a good definition of what a startup is would consider rate of growth (now and projections into the near future) rather than length of time since inception.

Re: Atlassian acquires Trello for $425M

#669
post #202

Earlier quoted context omitted.

My experience with Jira is that it depends very much on the managers and executive team who set it up and create the precedents on how to use it. Jira is so customizable and has so many features that it can be made into a sort of bureaucratic prison that's actively counter-productive for everyone except higher-level managers who just use it to generate countless reports. In the worst case, Jira can be used to institu…

True. I had to setup Jira for our team and must say it was an awful experience. Too many options, hidden in unintuitive places, awful (too verbose) documentation... Everything is just so difficult. Horrible UX. But it was still the best on-premise solution I could find. Trello on the other side is a delight to both setup and use. I think buying Trello was great move for Atlassian. No way could Jira compete with them…

Had to do the same thing but had a different experience. It was hard to dive in and took some time but now I understand and appreciate the core concepts. There are many abstraction layers ("[...] schemes") and IMO that is a good thing. When you customize workflows etc. you can do that without leaving supported areas. Creating and changing a workflow is very easy. Plus, JIRA has a good pricing.

With ~350 employees and many mixed teams using only Trello would be chaos. In key areas we need fixed workflows (-> JIRA).

Right now we are planning to add Wekan (FOSS trello clone) to our toolchain for workflows which are more dynamic (less "C follows B follow A" + smaller teams - e.g. innovation and some planning).

Post reply on HN