![[The AI Show Episode 144]: ChatGPT’s New Memory, Shopify CEO’s Leaked “AI First” Memo, Google Cloud Next Releases, o3 and o4-mini Coming Soon & Llama 4’s Rocky Launch](https://www.marketingaiinstitute.com/hubfs/ep%20144%20cover.png)
![Blue Archive tier list [April 2025]](https://media.pocketgamer.com/artwork/na-33404-1636469504/blue-archive-screenshot-2.jpg?#)
.png?#)
-Baldur’s-Gate-3-The-Final-Patch---An-Animated-Short-00-03-43.png?width=1920&height=1920&fit=bounds&quality=70&format=jpg&auto=webp#)
![Alleged Pixel 10 series wallpapers leak with vibrant colors and a strange new theme [Gallery]](https://i0.wp.com/9to5google.com/wp-content/uploads/sites/4/2025/04/pixel-10-wallpaper-leak-1.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1){kind=tracking}
![Apple to Split Enterprise and Western Europe Roles as VP Exits [Report]](https://www.iclarified.com/images/news/97032/97032/97032-640.jpg)
![Nanoleaf Announces New Pegboard Desk Dock With Dual-Sided Lighting [Video]](https://www.iclarified.com/images/news/97030/97030/97030-640.jpg)
![Apple's Foldable iPhone May Cost Between $2100 and $2300 [Rumor]](https://www.iclarified.com/images/news/97028/97028/97028-640.jpg)
On Trunk-Based Development
Something wild happened this morning. Bucket's CTO and co-founder, Ron '@roncohen' Cohen, who previously co-founded Opbeat and led engineering teams at Elastic, published a post on Trunk-Based Development (TBD) that hit the front page of Hacker News. People reacted... differently! "This sounds horrible — Why even use Git?" "I've never worked any other way in 20+ years..." TBD clearly is a controversial topic! Fun fact: you may already practice it. Ron wrote a follow-up post on Bucket.co to clarify some principles. Below are my key takeaways. TL,DR Trunk-Based Development != push to main You can still have code reviews and staging environments Focus on small, coherent code changes What is Trunk-Based Development? In software engineering, trunk-based development (TBD) is a strategy to manage git workflows that favours merging commits into the main branch even before the feature is fully complete, instead of the git flow that favours working on long-lived branches until features are 100% complete. Introduction to Trunk-Based Development flo merian for Bucket.co ・ Jan 30 #productivity #git #softwaredevelopment #featureflags Advanced Trunk-Based Development Principles It doesn't require pushing directly to main No, trunk-based development doesn't require pushing directly to main. While this might work in small engineering teams, code reviews remain essential for maintaining code quality. You can still use branches and pull requests (PR) while practicing TBD. You can still have code reviews and staging environments Yes, trunk-based development is compatible with multiple environments, including staging and pre-prod. You can still deploy your main branch to a staging environment for testing before pushing changes to production. Focus on small, coherent code changes Last but not least, it's all about creating coherent, small, and well-scoped code changes. This requires writing descriptive PR descriptions and breaking larger features into manageable, reviewable pieces. Wrapping up Trunk-based development (TBD) helps ship features faster. It doesn't require pushing code changes directly to main though. You can still use branches, pull requests, and code reviews. Above all, TBD is about creating small, frequent code changes. That's a wrap! If you enjoyed the read, please add some ❤️
Something wild happened this morning.
Bucket's CTO and co-founder, Ron '@roncohen' Cohen, who previously co-founded Opbeat and led engineering teams at Elastic, published a post on Trunk-Based Development (TBD) that hit the front page of Hacker News.
People reacted... differently! "This sounds horrible — Why even use Git?" "I've never worked any other way in 20+ years..." TBD clearly is a controversial topic!
Fun fact: you may already practice it. Ron wrote a follow-up post on Bucket.co to clarify some principles.
Below are my key takeaways.
TL,DR
- Trunk-Based Development != push to
main - You can still have code reviews and staging environments
- Focus on small, coherent code changes
What is Trunk-Based Development?
In software engineering, trunk-based development (TBD) is a strategy to manage git workflows that favours merging commits into the main branch even before the feature is fully complete, instead of the git flow that favours working on long-lived branches until features are 100% complete.
Advanced Trunk-Based Development Principles
It doesn't require pushing directly to main
No, trunk-based development doesn't require pushing directly to main. While this might work in small engineering teams, code reviews remain essential for maintaining code quality. You can still use branches and pull requests (PR) while practicing TBD.
You can still have code reviews and staging environments
Yes, trunk-based development is compatible with multiple environments, including staging and pre-prod. You can still deploy your main branch to a staging environment for testing before pushing changes to production.
Focus on small, coherent code changes
Last but not least, it's all about creating coherent, small, and well-scoped code changes. This requires writing descriptive PR descriptions and breaking larger features into manageable, reviewable pieces.
Wrapping up
Trunk-based development (TBD) helps ship features faster. It doesn't require pushing code changes directly to main though. You can still use branches, pull requests, and code reviews. Above all, TBD is about creating small, frequent code changes.
That's a wrap!
If you enjoyed the read, please add some ❤️
