11 ms·
Salesforce and Atlassian are the two big cloud things I have experince with. Both feel like they just swallow up products and duct tape them to their behemoth
by Waterluvian 6y ago
Salesforce and Atlassian are the two big cloud things I have experince with. Both feel like they just swallow up products and duct tape them to their behemoth in what results in a complete mess.
JIRA is a 22MB download any time I go to look at my tickets and the whole experience is grindy slow.
- Quarrelsome 6y agoI'm still amazed that JIRA redesigned the UI and chose to relegate the date the ticket was created to a "secondary piece of information". Every time I look at a ticket its like the 4th or 5th thing I check, its such useful information and they've allowed themselves to be so far removed from their principal use-cases its extraordinary. Unless maybe it was my org that foolishly decided to configure it away?
- zeckalpha 6y agoThe id is a proxy, ignoring cross project transfers
- pc86 6y agoMan, what happened to Atlassian? At some point in the not-so-distant past they were the gold standard, or at least I thought they were. Now they seem to be a cautionary tale.
- sjg007 6y agoCruising along. One issue though is that the integrated knowledge workflow is complex.
- nofinator 6y agoMy observation as a user is that it's still good if you are starting a new account from scratch. But if you have been using it for a decade and made lots of customizations and added plugins over the years, they get more clunky as they continue to update their product.
- awakeasleep 6y agoThis is it. I don't even think Jira is specifically bad. If someone was only using it for basic project managment and ticketing, it'd be acceptable. However, occupies the same niche as SAP or Oracle businessware. First, Take a service that must be ergonomic because people rely on it all day to do their job. Next, make the primary requirement the ability for managment and finance to run reports. Then, outsource it to a company that wants to add custom web frameworks on top of a decades old project. Finally, graft on decades of customizations done by different generations of contractors.
- ianhowson 6y agoYep, agreed. If you can admin your own Jira instance and keep the fields and plugins to exactly what you need, it's pretty nice. I keep going back to it for the customizable workflows and fine-grained access control. Unfortunately, every corporate Jira instance I've ever worked with has been overrun with every possible field possible, an unnecessary and constantly shifting mishmash of plugins and horribly slow access. You're paying the price for all of that cruft that you don't need and which can't be removed because "maybe someone wants it."
- gtyras2mrs 6y ago> every corporate Jira instance I've ever worked with has been overrun with every possible field possible I've seen multiple different fields for the same value, each of them created for their specific team. The instance is slow AF most of the time due to the bloat and often I can't even assign a sprint to a JIRA because the field doesn't load anymore.
- andreimackenzie 6y agoAgreed. Jira makes it easy to add a new field, plugin, or workflow step for a particular use case, but it is much more difficult to determine if an existing field/plugin/workflow step can be safely removed. As a result, everyone is afraid to touch it, projects accumulate cruft over the years, and it degrades the entire workflow. The problem is especially bad if there is shared ownership of JIRA, and therefore everyone feels empowered to add, but nobody feels responsible for the dirty work to clean up the mess from time to time. My company had resisted the urge to bolt on additions more than most. We recently migrated from Cloud to on-prem Server as a result of being acquired, and it is amazing how much zippier our project is compared to some of the peer projects that have accumulated cruft.
- threeseed 6y agoRevenue was $1.6 billion in 2020, up 33% from $1.2 billion for 2019. Growing at that rate at this point in your company's lifecycle is pretty extraordinary. So not sure why you would consider them to be a cautionary tale. As for what has happened to them. They have been on an acquisition binge the last few years e.g. Trello, StatusPage, OpsGenie, Mindville etc. And as mentioned above they have been rewriting their UI in a new React framework called Atlaskit. I also used to think Atlassian was a pretty poorly run company but then you look into it and actually the opposite is true. Although they did let Github, Gitlab, Slack dominate them. Next few years will be interesting as Gitlab is moving very fast into their space.
- ProAm 6y agoSales and Revenue do not always equate to quality and user experience. All these companies when they get to this size start to lean on M&A vs build it yourself. Look at the history of Oracle, Microsoft, IBM and you'll see the same pattern. Slack is the new Sharepoint, everyone uses it but no one really wants to and it doesn't really fit the bill but everyone else is doing it so companies adopt it.
- quickthrower2 6y agoSlack's value is in selling the idea of async chat to managers and making it mainstream. I don't feel as nauseous using it as Sharepoint, but it does seem to be buggy and crashy in places.
- Rillen 6y agoFor me slack is a very simple deal: Microsoft Teams Chat UI is garbage. It uses a lot of space, i can't just have a list of channels, no i need groups etc. It even doesn't matter to me if its slack or hipchat or matrix or whatever. I don't know why we migrated to slack. I don't get why Teams doesn't provide a lightweight chat typical UI. I would just switch to Teams. After all video calls are much better on Teams and more stable. But then Slack integrated Teams and Zoom. They clearly don't want to compete in this area and i also don't get why.
- brightball 6y agoAt least they haven’t messed with Heroku.
- craigkerstiens 6y agoI'm not sure that's actually the case at this point. Given it is not 10 years into the acquisition that is a pretty long time for it to still not have been engulfed in the mothership, but that time seems to mostly be up now.
- cpursley 6y agoGood thing we have competitive (and cheaper) options now including Digitalocean app platform and Render.com. I'm actually surprised it took this long to match Heroku (and beat them on costs).
- pgm8705 6y agoTrue, but neither are really optimal for serious production use. I've looked at them both extensively as I would love to move off Heroku due to pricing. DO App Platform is still really immature and lacking in a ton of areas. Render is much more polished from a usability standpoint, but AFAIK they don't have any sort of High Availability offerings and have had significant downtime recently. Heroku, on the other hand has been a hassle-free solution for my company over the past 7 years, and short of a few outages (which were actually the fault of AWS from what I remember), it has been absolutely reliable.
- cpursley 6y agoYeah, Heroku is awesome. I'd stay with them (despite the price) if I could run distributed Elixir.
- anurag 6y agoJust came across this comment (I work at Render). We did have 2 hours of downtime on 9/11 but it was the only big uptime incident in 2020, and we haven't had any major incidents since (even when AWS was down for 5+ hours). We've worked hard to incorporate reliability lessons learned from building the platform at scale especially as we've grown [1], and I hope you'll give us another chance. If I can do anything else to help, my email is my HN handle at render.com. [1] https://www.tfir.io/more-than-100000-services-created-on-zero-devops-cloud-render/ https://www.tfir.io/more-than-100000-services-created-on-zer...
- mdoms 6y agoI worked on that new Jira UI (codename Bento) and it was a constant source of embarrassment for me. I pushed hard to get the powers that be to focus more on performance and payload, but it was a Sisyphean task. It was perhaps the most demotivating job of my career because I disagreed with virtually every decision that was ever made with regards to that UI, from technology choices (the inane choice to use RxJS despite literally no valid use cases, the 5+ Redux stores in the same page, etc) to UI layout decisions (insane whitespace, the baffling choices about which things go in the right hand gutter...). The components were mostly handed down to us from a company-wide UI team whose main design goals were to bring commonality across all Atlassian products. This is a worthwhile goal, no one thinks that it makes sense that Atlassian has different editors and even markup languages between (and even within) products. But the result was dog-slow overweight components like the Atlassian editor which tried to be everything to everyone. So when you need to bring in a monolithic highly-customisable 12mb+ component for every text edit field then things spiral out of control quickly. One cool thing, though, is that these components are open source[0]. And it looks like some performance/payload work has been done since I left, thank god. In my new job I use Jira Server which hasn't been infected with the updated UI, and it's a shame because other than that terrible UI there have been big meaningful updates in Jira. But I'm dreading our inevitable migration to Cloud. [0] https://bitbucket.org/atlassian/atlaskit/src/master/ https://bitbucket.org/atlassian/atlaskit/src/master/
- stevoski 6y agoThis is fascinating to hear. Sometimes with Jira updates, I have to ask myself “What WERE they thinking?” It’s good to hear that actually some people (well, at least one!) inside the org ask this too.
- threeseed 6y ago> I pushed hard to get the powers that be to focus more on performance and payload If I was in Atlassian's situation this would be the last thing to focus on. a) This is the biggest ever rewrite of their most important products. In this situation maintaining feature set compatibility is always going to be priority A, B to Z. b) Their paying customers are mostly in the enterprise space who have very fast internet and stable environments i.e. payloads are quickly cached.
- slater 6y agoI hate to be the "but it looks so easy" guy, but why are all these "behemoths" such a huge mass of things for essentially CRUD-y stuff with e-mailing bolted on? (and yes, you could water, i dunno, facebook down to that, but still, these are... trouble ticket systems..? what am I missing? Scaling?)
- hobonumber1 6y agoJIRA offers an almost limitless amount of customization to fit any workflow. I think the custom attributes/fields/reporting part of it adds a lot of complexity.
- bingo_cannon 6y agoScaling is only half of it. There is a lot more to Jira than just CRUD over a few entities. It's trying to be issue tracking and project management rolled into one. For example: - Workflows - Access control over fields - Custom fields - Release management - 3P plugins and integrations - API access I am far from being a fan of Jira but they do have a rather large set of features. Every time I evaluate the hottest new issue tracking and/or project management solution, there is something lacking as compared to Jira.
- slater 6y agoGot it, thanks.
- sethhochberg 6y ago
- kbos87 6y agoSpot on. This also feels like a strategy that won’t age well. It’s tough if not impossible to deliver great UX from a bunch of acquired pieces. Slack’s relatively short path to wide adoption is evidence that the world is less and less tolerant of poor UX, even in the context of business software.
- ntsplnkv2 6y agoThey're of the same ilk as Oracle/SAP. They need to absorb things so their sales team can say "oh we have X feature" regardless of its actual implementability and just leave it to the consultants to struggle and somehow implement a half baked solution that doesn't work in the end. Oh but that's how they make money also. More products, more features, more crappy integrations = more service contracts, more consulting work, etc. All a huge scam that enterprises are forced into because they don't want to be "left behind in the digital economy."
- natchy 6y agoAlso, these companies have MASSIVE sales forces (no pun intended). By acquiring a decent enterprise product and throwing teams of sales guys on it they can make a lot of money. Returns aren’t as good if acquisition is high, like slack will be.
- threeseed 6y agoNote that Atlassian doesn't have an enterprise sales team. They are a pretty notable company in startup history since they were the first to be hugely successful at using the self-service model for enterprise sales.
- cyberpunk 6y agoThey do have a partner system however which is widely used, you need a number of staff who are atlassian certified on your staff then you become a <some level> partner, and get a cut of the sales you make. A lot of small(ish) firms are making reasonable money doing this sort of thing; I'd count them as enterprise sales ;)
- Rillen 6y agoIts also just much more efficient. One central high quality HR Team can scale easily in a big org while the same amount in small companies need spend more on HR. And its not just HR of course. I wouldn't even trust small companies to build a modern and secure cloud product. While big companies have their own Security Teams and are able to afford a normal security audit, for a small company that means 1. much higher cost in relation and also binding of personal they might not have. I have worked in a very small company which basically couldn't spell security. And i'm now working in a very big company. There are plenty of people who also can't do that but there are teams only for security. I don't have to justify now that i'm doing things securely. Thats how it is. My manager will not sign the risk away; He actually can't and people are not keen of asking upper upper management for that.
- tdons 6y agoI didn't believe the 22 MiB download but it's true. 156 requests and 26 MiB with an empty cache. Oh my.
- rplnt 6y agoAnd that's a site without any etxernal tracking or ads. No images either. But their horribly inconsistent UI and UX a big tell why it is this way. They simply serve you multiple versions of their website, each for different component. And together it's a giant mess.
- spurgu 6y agoYeah, just checked a random ticket and got 223 requests and 37.6 MB of resources, DOM loaded in 19.48 seconds (granted I'm on a slow connection)... > But their horribly inconsistent UI and UX a big tell why it is this way. It's insane how the editor changes between creating a task description, to editing a task description, to writing a comment. Like three separate teams with loose guidelines created them. In reality it's probably more like 7 teams. I hate Atlassian with a passion and the only reason I touch it is because I'm a corporate slave.
- aitchnyu 6y agoI've witnessed internal confluence pages with Facebook likes.
- georgiecasey 6y agoJIRA is the slowest website I use in current year. If it was a consumer site like Youtube or Twitter, I'd long stop visiting. You can feel the gears slowly turning whenever you click something. When I click the wrong button I get that pang of anxiety like you used to get when you accidentally opened Photoshop back in the day and had to wait the 20 seconds for it to load.
- rplnt 6y agoCreating a ticket in Jira is a pain I try to avoid. I've never seen a worse UX for something that simple. I hate it with passion, and my computer does too, always spinning up cooling fan. Then I create it, and of course the formatting us fucked up. Every single form has a different flavor. Preview shows something else to what will show after submit. You press edit and you see a completely different syntax. One couldn't make the experience so bad even if they tried.
- loufe 6y agoI'm leading implementation of a software up at a remote arctic mine site (geostationary satellite internet) and have to manage our issues on the vendors Jira implementation. It takes about 5 minutes to load the site the first visit. It's dreadful.
- throw93 6y agoCan you use JIRA APIs through Postman instead of UI in your case? It won't be super convenient but at least it would be faster I suppose.
- otabdeveloper4 6y agoNah, Slack is way slower than Jira for me. (Two super-slow things combine to make the ultimate slow thing - looks like the aquisiton makes sense after all!)
- georgiecasey 6y ago
- llimos 6y agoWhat they have in common is that the people ordering it are not the people using it. These companies focus on the former, who want different things to the latter. Which sucks for the users but it makes sense for the vendors.
- justin_oaks 6y agoIndeed. This reminds me of the tweets about why enterprise software is like baby clothes: https://twitter.com/random_walker/status/1182635589604171776?s=21 https://twitter.com/random_walker/status/1182635589604171776...
- rotten 6y agoAnd yet at my last two startups, when we could literally pick any product on the market - there was tremendous pressure from product, project management, devs, and the business to use JIRA "because it worked just fine at the last place I worked and even if it didn't, at least I'm familiar with it". I'd love to see a killer Jira replacement that people don't say "in spite of how ugly and slow and barely useable it was, I still love Jira".
- otabdeveloper4 6y agoWe finally migrated to Youtrack and everybody is happy.
- quickthrower2 6y ago22MB ain't so bad ... oh you mean to view the page!
- gbuk2013 6y agoWork anecdote: Before I discovered “openssl speed”, I used JIRA to find race bugs in JS tests - loading up a JIRA ticket while running the test in a loop would spike the CPU for long enough to trigger the race. :) Man, that UI is such a slow resource-hog of a bloat-ball.
- bamboozled 6y agoI hate JIRA for this reason, and just the insane level of complexity it almost instantly breeds. There's just too many ways to "agile" in JIRA, every project/program manager I've worked with turns it into a Frankenstein immediately.
- jokethrowaway 6y agoYou're right, slack will fit just right!
- peanut_worm 6y agoJira has some of the most staggeringly stupid design decisions I have ever seen. I get so frustrated trying to do anything in their interface and it lags so badly on my outdated office hardware.
- dboreham 6y agoStrange how no bug system is remotely as good as Bugzilla c. 1997 was.
- burnte 6y agoWe got fed up with Salesforce's absusive behavior to smaller companies, or at least the behavior of the finance team we were assigned to, and left. We did an emergency Salesforcectomy in 30 days, switched to a new product, and honestly everyone who uses it is a lot happier. SF buying Slack worries me for the future of Slack.
- enra 6y agoWorking on something faster: https://linear.app https://linear.app
- ing33k 6y agoHeroku which was acquired by Salesforce seems to be doing ok ?
- cjonas 6y agoHere's a fun exercise in technical debt. Navigate to the Salesforce Idea Exchange and upvote any idea. You will be redirected no less than 13 times and after which you will no longer be on the page you started on.
- jirasux2020 6y agoYou may like https://whyjirasucks.com/ https://whyjirasucks.com/ You can contribute too!