I think programming is made worse today by how programmers are managed. Agile, Kanban, Scrum, JIRA - they’re all there so upper management can get a sky high view of what’s going on, but it’s all based on “estimates” that are often shots in the dark. They might give the CEO a warm, fuzzy feeling, but they’re often based on fiction. And I waste half my day in “planning poker”, “retrospectives”, “standups” - yuck.
> And I waste half my day in “planning poker”, “retrospectives”, “standups” - yuck.
Only half a day? I've seen these take, cumulatively, more than a day.
Then add in the requirement that changes/proposals needs a technical document review (and a followup if necessary), that any planned feature needs input from everyone involved, that some proposals which may touch some other teams work needs their buy-in (and so you have to schedule proposal presentation with them), and you can easily see a sustained 25+ hours per week used only for meetings.
