The article explores the evolution of git branching strategies, using a narrative approach to illustrate how Ashley, a fictional software entrepreneur, navigates these methodologies from trunk-based development to more complex models like GitFlow, and eventually back to simpler workflows with GitHub Flow. Initially, Ashley started with trunk-based development, where all code changes were committed directly to the main branch. As her business grew, she adopted release branches to manage multiple software versions, which led to the complexity of hotfixes across different versions. To address these challenges, she incorporated GitFlow, introducing a develop branch to stabilize new code before releasing it. However, as her company transitioned to a Software-As-A-Service model, the need for complex branching diminished, allowing her to streamline the process with continuous integration and deployment directly from the main branch. The story underscores the importance of choosing a branching strategy that aligns with a company's specific software lifecycle needs, emphasizing that simpler models often suffice when software is continuously delivered, particularly in cloud-based environments.