Re:You don't want to hire "the best engineers"
by 010101010101 on Tuesday September 02, 2025 @07:32PM
(#45110468)
The best managers I’ve ever had didn’t use Jira, because they didn’t use much of anything at all, and more senior engineers were trusted to manage work streams and run projects without needing to conform to a process demanded by someone not directly committing code.
Jira might turn terrible managers into mediocre ones, but it also turns good managers into mediocre ones too.
Re:You don't want to hire "the best engineers"
by jama211 on Wednesday September 03, 2025 @08:04AM
(#45114740)
How did those senior engineers assign and track work to less senior devs in the team in your case out of curiosity?
Re:You don't want to hire "the best engineers"
by 010101010101 on Wednesday September 03, 2025 @09:11AM
(#45115321)
Depends - sometimes with simple Jira boards, sometimes with other tools like Smartsheets or Air Table or a simple spreadsheet, sometimes with post-its and a white board, sometimes with no system formal or otherwise. My point is less about Jira specifically and more about tool/process dogma (although I do think Jira is the tool of choice for most “we must used the Agile Toolkit Scaled Enterprise Framework Productivity System MegaProcess for all things!” types than others, mostly because of having been around forever and because of Atlassian pitching organizations to use Jira workflows for compliance as if it were uniquely capable of tracking when someone clicked a button in a UI).
Re:You don't want to hire "the best engineers"
by jama211 on Wednesday September 03, 2025 @03:13PM
(#45119447)
Fair enough, thank you!
Re:You don't want to hire "the best engineers"
by tikhonj on Wednesday September 03, 2025 @09:33AM
(#45115598)
One way is for senior engineers to give junior folks well-defined areas of responsibility, and then not worry about assigning and tracking small tasks within that. The more senior folks explain and motivate what we need and talk through what the interfaces around the area are and how it fits into the broader work of the team, then help as-needed.
Instead of trying to "track" work in terms of tasks, you keep up with the state of the system by understanding the state of each area. Which is pretty natural to do since you'd be helping with design discussions, code review and some pair programming and debugging.
You can get a lot done by talking and by looking.
Jira helps turn terrible managers into mediocre ones, it at least forces them to write down what needs to be done and let’s me prove I’ve done the work back to them later when they inevitably forget.