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:
- read and follow the programming.dev code of conduct
- no flamewars
- mark your unjerks
- only programming related content allowed
- link to the original source
- do not mention this community in places like hackernews, lobste.rs, or the general programming communities on Lemmy where we source jerk material from.
founded 2 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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