"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.

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.

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.