this post was submitted on 31 Mar 2026
139 points (99.3% liked)
Programming
26304 readers
692 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When developing code for first release, we had a dedicated HIP Sprint (Hardening, Innovation, Planning) and we had the most productive team in the company. Other teams were struggling cause they were just using the HIP as another Sprint. So what did we do? Got rid of the HIP, naturally. You see, some teams weren't using it and it's unfair to those teams that we're not doing work when they are. Now everyone's suffering!
Also had legitimate agile practices (budgets are for HR, work on what you need to work on and let someone else worry about paying for it) and we were the most productive team in the company. So, naturally, they need to get a bunch of C-suite guys to come over and run things cause it would be really embarrassing for them if they weren't involved in the new hotness. Naturally, though, we gotta go back to funding buckets, cause those c-suite guys don't understand why they got to talk to the developers when they want something fixed instead of handing things down from on high. Oh no! Suddenly all these issues are popping up in the workflow, guess we gotta force in ai to fix the problems.