I love the workflow. In fact, it kind of mirrors the one I settled on myself in my Cloud DevOps work. I just published my book (vibe coding: build cloud infrastructure at the speed of thought) on this same topic. It's good to know it works for multiple realms in Software engineering.
I learned a lot from this. Thank you! Question about the tests you prompt for -- you ask for the happy path and two "edge" cases. Does "edge" really mean edge as in "boundary" or "uncommon", or does it actually mean error path or exceptions?
Thank you. Loved every bit of this post.
I use LiveReview, a Source-Available AI Code Reviewer, which I built for myself.
The specialty with LiveReview is that it triggers during git pre-commit automatically.
And it also marks a commit as reviewed or not for posterity.
To be honest - despite being the builder of the tool, I was sceptical of how useful it could be.
But with experience, I’ve found that LiveReview precommit has caught me 100s of issues in a matter of months.
This makes the team level PR review easier later because sanity checks have been done at commit time itself.
You can check it out here:
https://hexmos.com/livereview/
I love the workflow. In fact, it kind of mirrors the one I settled on myself in my Cloud DevOps work. I just published my book (vibe coding: build cloud infrastructure at the speed of thought) on this same topic. It's good to know it works for multiple realms in Software engineering.
I learned a lot from this. Thank you! Question about the tests you prompt for -- you ask for the happy path and two "edge" cases. Does "edge" really mean edge as in "boundary" or "uncommon", or does it actually mean error path or exceptions?
Really well put workflow, I appreciate it! The only thing I do differently is dictating the prompt instead of typing it. Guess I’m a bit lazy 😄