I deployed code during my morning walk.
Walking used to be my ideas time. Good for learning, bad for ๐ฅ๐ฐ๐ช๐ฏ๐จ.
Yesterday, I tried Google Jules. The workflow is simple:
โข Open Jules on my phone browser
โข Speak what I want built. It clones, code, tests, and pushes.
โข I review and merge at home.
Three use cases have worked well:
๐๐ผ๐ฐ๐๐บ๐ฒ๐ป๐๐ฎ๐๐ถ๐ผ๐ป (easiest): "Add a professional README.md covering installation, usage, and architecture." Low risk, high quality, nobody likes writing docs anyway.
๐ง๐ฒ๐๐๐ถ๐ป๐ด (solid): "Extend test cases covering uncovered code paths in the same style." Low risk, medium quality, nobody likes test generation either.
๐๐ฒ๐ฎ๐๐๐ฟ๐ฒ ๐ฐ๐ผ๐ฑ๐ถ๐ป๐ด (risky): "Format dates nicely and add CSV export." Higher stakes, but automated tests provide a safety net.
So now, one walk now equals one merged PR. (It used to take 2 hours even with ChatGPT/Claude helping).
Sure, there are problems. It politely removed stuff from my existing README and I manually reverted. Frontend tasks still need visual QA, which is tricky on mobile.
But what I'm learning is that AI coding agents aren't just faster ChatGPT. They're junior developer who never sleep. They run tests and pushes actual branches. With clear requirements and good reviews, they're productive.
I suggest you ๐๐๐ฎ๐ฟ๐ ๐๐บ๐ฎ๐น๐น. Pick a low-stakes repo, add docs, write a few test cases, ๐ต๐ฉ๐ฆ๐ฏ add features.
Here are some of Jules' PRs I merged:
Documentation: https://lnkd.in/gYaEkHqP
Test cases: https://lnkd.in/gGWD5U_n
New features: https://lnkd.in/grb7iHfJ
Full prompts: https://lnkd.in/gjEDCnWe