2 ms·
> Considering that there are so many variables at play, it's a very flawed conclusion. You don't have enough data. It's not magic. You're just choosing to see i
by lmm 3y ago
> Considering that there are so many variables at play, it's a very flawed conclusion. You don't have enough data. It's not magic. You're just choosing to see it as you please.
I've been working in software for about 15 years across a wide range of companies and industries. JIRA or not is the best single indicator I've found for whether a workplace will suck (in particular, switching to JIRA is the most reliable indicator of when it's time to leave).
> Well then take it out? Giving you a gun doesn't mean you need to kill someone. Responsible adults? If you buy the tool at least there should be some effort in making it work?
> Again, you speak as though someone died because you had a gun - not because you killed them. Maybe consider that the company should be implementing a process or system and buying a tool to facilitate. They need to then set that tool up. If all they do is buy the tool and sleep that's on them.
I can't take it out, because JIRA only lets managers/admins/what-have-you do that, and they aren't the people who have to fill in the pointless fields and don't care.
A properly designed gun will have safety features (there's simply no excuse for not being able to undo the transition you just did, that's the equivalent of having a hair trigger and no safety), and a responsible gun store will offer safety training to buyers.
Good defaults are important, and other tools in this space manage to get them right.