this post was submitted on 20 Feb 2025
63 points (100.0% liked)

Programming Circlejerk

130 readers
1 users here now

Community to talk about enlightened programming takes

Rules:

founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] onlinepersona 2 points 1 month ago

Trust me, people still call it trunk based development. Just like "agile" has many forms, trunk based development does too.

Managers will often read about some process, tech, or strategy and tout it as the solution to their problems without understanding context nor wanting to invest in what's actually required for a successful implementation. For example trunk based development should have automated testing, a deployment and a fallback strategy. And if you're working on something with hefty features that you can't slice, feature flags or something similar are probably required. Not giving the team time to develop a strategy to implement that is a great way to mess up a product.

Anti Commercial-AI license