One of the fundamental challenges in software engineering is managing and minimizing complexity. This challenge is not just a theoretical concern; it has real and tangible impacts on the pace of development.
I can see which way the wind is blowing here, but fwiw, I use graphite at work. And I like it!
I largely use it to help me break up changes into clean PRs after doing a bunch of exploratory programming. I still iterate on my feature quickly, but my coworkers get small, focused PRs. It really is easier to review when I get PRs that are divided into, say, database migrations vs business logic changes vs refactors.
And to be fair, it’s all stuff you can do with git branch and git rebase, but the graphite cli automates it so I don’t have to do much besides commiting like code together.
Anyway, yes, still an ad. This is just two cents from somebody that has actually used graphite.
I can see which way the wind is blowing here, but fwiw, I use graphite at work. And I like it!
I largely use it to help me break up changes into clean PRs after doing a bunch of exploratory programming. I still iterate on my feature quickly, but my coworkers get small, focused PRs. It really is easier to review when I get PRs that are divided into, say, database migrations vs business logic changes vs refactors.
And to be fair, it’s all stuff you can do with
git branchandgit rebase, but the graphite cli automates it so I don’t have to do much besides commiting like code together.Anyway, yes, still an ad. This is just two cents from somebody that has actually used graphite.