it's tough for people here to admit, but AI is good at summarizing and that includes commit messages and PR fields
but that does NOT mean you get to skip understanding the code & whipping the AI in line during implementation
my preferred workflow:
- think hard about the problem before touching the keyboard
- back and forth with the AI, swatting down bad implementation ideas and poking holes
- settle on a detailed implementation plan
- let the AI go for however long it needs to (usually minutes, sometimes hours)
- review, iterate, test
- "this looks good, commit in focused chunks and create a PR"
- review commits & PR summary, hand edit for clarity
but that does NOT mean you get to skip understanding the code & whipping the AI in line during implementation
my preferred workflow:
- think hard about the problem before touching the keyboard
- back and forth with the AI, swatting down bad implementation ideas and poking holes
- settle on a detailed implementation plan
- let the AI go for however long it needs to (usually minutes, sometimes hours)
- review, iterate, test
- "this looks good, commit in focused chunks and create a PR"
- review commits & PR summary, hand edit for clarity
Former co-founder of Volition (govolition.com, acq by Siemens) and Plethora (software defined CNC factories).
I'm into retro computers and homebrew pinball machines.
San Francisco by way of Pittsburgh, PA
twitter.com/jherrm
jherrman.com