"We built the plane while flying it" is NOT AN INVITATION to have sloppy execution. When *already successful* founders say it in, it is a post-hoc account of the reality and constraints they survived. If you ASPIRE to build the plane while flying it, you will not become one of those founders.

So sad this is going away!

Also, if you were a rapper, ahoy hoy is your ad lib :p

With stacked PRs in Graphite you can:
1. Create one PR which ONLY renames variables. The reviewer can turn their brain off knowing there are no logic changes.
2. Second PR contains all new logic. Since all variable renames were taken care of, this PR is much more clean and readable for the reviewer.

Graphite stacks can make your pull requests much more understandable to the reviewer. Here's one situation:
- You want to add new functionality to a particular class.
- The past variables were named with only the old functionality in mind and will cause namespace conflicts/generally be confusing.

So many founders forget that the next best alternative to their startup is often not another startup. In dev tools the convo is always "build vs buy" and sometimes the "build" option is very attractive.

Every example of "I succeeded by breaking the rules" needs to be served alongside five examples of "I broke the rules and got absolutely blasted" for a startup advice blog/book/podcast to not be considered irresponsible. Survivorship bias is incredibly strong.

Just onboarded to Graphite and the engineering velocity gain from small, readable, stabled pull requests is mind blowing.