45 ms·
> And yet, as if by magic, they consistently happen at workplaces that use JIRA, and not at workplaces that don't. Considering that there are so many variables
by re-thc 3y ago
> And yet, as if by magic, they consistently happen at workplaces that use JIRA, and not at workplaces that don't.
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.
> If it were manual, no-one would stop me submitting the form with the field not filled in where it doesn't make any sense.
It just works both ways. You can't have everything. Yes no 1 stops you submitting the form but you also potentially miss a lot of things. When it's discovered the context is lost or the friction is too high or they don't even know it's missing to begin with.
You might as well just not submit it then.
> They are unnecessary. Management doesn't actually use them and they don't even make sense for a lot of issues
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?
> Sure, but most workplaces don't have a magic trapdoor where if you accidentally pushed the wrong elevator button then you can't come back without a manager letting you out.
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. A lot of larger companies do hire dedicated specialist to configure and maintain workflows and the like.
So I'm not saying JIRA is the best or anything. It's just never designed as something that works out of the box for everyone. A lot of the "enterprise" alternatives are way worse and that's what it won over. I'm sure it can do a lot better but again I don't see it as the problem in most cases. It's like if you buy a Mac and tried to use it as a PC and complained about not being able to swap the GPU then I'm not really sure it's the Mac's fault.
- 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.