Tech Monk·Oct 9Git is a Tree with Trunk, Root, Branches and LeavesMost people only learn the trunk. Here is the whole tree
Codecraftdiary·Jul 26Merge Conflicts Are a Process Problem, Not a Git Problem — CodeCraft DiaryMost developers treat merge conflicts as a Git problem.
Shubham Sharma·Jul 26Branching Is BorrowingFive branch types, four merges and a review gate. How we industrialised waiting, then called it rigour.
Codecraftdiary·Jun 28Automated Testing Strategies for Trunk-Based Development: How to Build a 10-Minute Pipeline —…If you’ve been following my recent posts, you already know I am a big fan of Trunk-Based Development (TBD), tiny pull requests, and…
Praveen Padamati·May 13Trunk-Based Development with Feature Flags: A Practical Enterprise Release ModelHow enterprise teams keep main moving, protect production, and still meet release governance
Shivam Ashtikar·Apr 8The Missing Piece: My 4-Year Journey Implementing Trunk-Based DevelopmentThe recent ByteByteGo deep dive into how Spotify ships to 675 million users is a masterclass in platform engineering. They call it the…
Codecraftdiary·Apr 8Trunk-Based Development: Why Most Teams Think They Use It (But Don’t)Trunk-Based Development sounds simple.
Praveen Padamati·Jan 23We Thought We Were Doing Trunk-Based DevelopmentUntil Production Taught Us Otherwise
Ram Taylor Abigadol·Dec 25, 2025Trunk-Based Development: The Operational Regulations of Continuous DeliveryTrunk-Based Development: The Operational Regulations of Continuous Delivery
