I went full circle – from IC to EM, and now I'm back. I focus on technical leadership and internal platforms.
👋 Hey! I'm Jakub Beneš, a Software Engineer based in Prague. I'm passionate about scaling engineering, organizational design, and leadership. I'm a huge fan of web technologies and modern approaches within this field. While I'm a strong contributor on the frontend side, lately, I've been focusing more on the entire stack and infrastructure because there's often low-hanging fruit that can deliver a massive impact – and I enjoy seizing such opportunities. I'm not sure if I'll ever start liking YAML, though. 🤓
Markdown supported · ⌘↵ to post
Ezequiel Leonardo Castaño
I believe the definition of trunk-based development presented is not aligned with the widespread one. Trunk-based development is a methodology where "everyone works in the main branch" and, if there are other branches, they are short-lived, i.e. less than a day.
That would render Stacked PRs as basically the opposite of trunk-based development, since to stack PRs, one assumes a single PR (and thus a branch), will live for several days because otherwise it would not be worth the overhead.
Have a look a this talk from MSFT: Git patterns and anti-patterns for successful developers : Build 2018