Comment on When did programming become "coding"?
Powderhorn@beehaw.org 6 days agoI ended up very happy I didn’t go into software once I heard the hell of agile and Jira. Like, I can do this all in Python … what are y’all talking about?
Agile just sounds like a stupid modeling method. Has anyone ever said without irony “we’ll get it better next sprint”? Really? You want better software as a software company? Thank god I was sitting down.
Of course you fucking are. If your company is hoping for reversions via this may as well die. The whole point is control, not output, efficiency or quality.
bryndos@fedia.io 6 days ago
Yep. I'm sure its fine in small competent teams with a workflow that they're comfortable with.
But any large organisation I've worked in involves clueless middle managers and teams with some people who really should move on. Agile seems to make incompetence of managers less obvious, and makes them less accountable. Seems to remove control over both the workflow, cost base and the quality of product/service.
It also gives them this great universal technique for problem solving.
"We found that Task X is not being done right" . OK we'll write a job title "X doer". Appoint person who doesn't really know what X is, but neither does the interviewer. Make this person go to 'stand ups' and assign them some jiras. 3 months later, they wonder why X is still not being done and why their new hire left already.
The root cause for sure is incompetent management not the methods. But their project method seems to protect them and impair actual improvement.