4 ms·

The interface used to be simpler and less in the way of getting things done. Then they added personas, UX and tried to "help" the user. You now need more clicks

by loopz 6y ago

The interface used to be simpler and less in the way of getting things done. Then they added personas, UX and tried to "help" the user. You now need more clicks to accomplish the same stuff while information is more hidden than before also. There's no way to cater every possible workflow without feature bloat. However, the space is ripe for simpler, more accessible solutions that supports work across multiple projects.

echelon 6y ago
It's not for engineers. Or anyone in particular. They're building to check off boxes in order to sell top down to C-level execs that never touch the stuff. Atlassian products are all like this, and each one is a horrible trash fire. Confluence is the worst wiki product I've ever used. Gross syntax, slow, clunky plugin system, awkward permissions. Install MediaWiki and be done with it. Bitbucket is slow and feels like it's from the 90s. It doesn't seem to do multithreading well - sometimes force pushed branch rebases pick up a new, unrelated author. A bug that hasn't been fixed in years, and only one of many. How many times will merging not actually work? Jira is a special kind of hell. It's like every team needs their own embedded Atlassian solutions engineer to get it into a usable state. Not an EM or PM, but a specially dedicated role just to deal with Jira nonsense. Why even bother? Atlassian is like Salesforce for business process, but if it were written by all-remote temp contractors churning through Jira tickets themselves.
- pm90 6y ago
  Agree with this. My hypothesis is that they’re just ridiculously slow at adopting newer UX principles. The product was successful initially (good for them) and it was just never made much better. The horrible response times and user hostile UI is shocking, especially if you look at their competitors. It gets in your way all the fucking time. But because they’re embedded in enterprises they don’t need to change much. It’s a big mess.
- mgkimsal 6y ago
  > Confluence is the worst wiki product I've ever used. BUT... the direct integration with the ticket system - highlight a list, and make linked tickets (which keep the status info 'live' in the confluence doc) is pretty powerful, and allows a lot of people to keep their business docs, and get status updates without ever having to learn other parts of the system.

by loopz 6y ago

echelon 6y ago

It's not for engineers. Or anyone in particular. They're building to check off boxes in order to sell top down to C-level execs that never touch the stuff. Atlassian products are all like this, and each one is a horrible trash fire. Confluence is the worst wiki product I've ever used. Gross syntax, slow, clunky plugin system, awkward permissions. Install MediaWiki and be done with it. Bitbucket is slow and feels like it's from the 90s. It doesn't seem to do multithreading well - sometimes force pushed branch rebases pick up a new, unrelated author. A bug that hasn't been fixed in years, and only one of many. How many times will merging not actually work? Jira is a special kind of hell. It's like every team needs their own embedded Atlassian solutions engineer to get it into a usable state. Not an EM or PM, but a specially dedicated role just to deal with Jira nonsense. Why even bother? Atlassian is like Salesforce for business process, but if it were written by all-remote temp contractors churning through Jira tickets themselves.

pm90 6y ago
Agree with this. My hypothesis is that they’re just ridiculously slow at adopting newer UX principles. The product was successful initially (good for them) and it was just never made much better. The horrible response times and user hostile UI is shocking, especially if you look at their competitors. It gets in your way all the fucking time. But because they’re embedded in enterprises they don’t need to change much. It’s a big mess.
mgkimsal 6y ago
> Confluence is the worst wiki product I've ever used. BUT... the direct integration with the ticket system - highlight a list, and make linked tickets (which keep the status info 'live' in the confluence doc) is pretty powerful, and allows a lot of people to keep their business docs, and get status updates without ever having to learn other parts of the system.