Rendered at 02:35:24 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
mackatsol 39 minutes ago [-]
More testing is better, so far! I'm using the same red-green-refactor TDD idea, and having Claude use Superpowers code review and running Coderabbit CLI on it all before pushing to CI/CD, which also runs a series of tests (mostly security ones).
Someone else posted that whenever something broke they would ask 'Why was it built that way?' to try to have the bot fix it's own coding patterns.. as well as adding a regression test to ensure it did not happen again.
I also have it do dry-runs and then do live on one item before batching. Catches a lot of things!
Oh, and insist that it RTFM's the API if you're using one.
mr1337 2 hours ago [-]
Testing is not a formality. In fact, it's better and easier than ever. Tell your agents to develop your code-base with Red-Green-Refactor Test-driven development. Write failing tests first and run them, then write the code to make the tests pass, then refactor the code as needed. I used to hate writing tests before, but now that I can offload that (and the development, honestly) to AI, it's nothing to keep up with it. Your codebase quality will increase with TDD, because it will reduce the number of things that inadvertently break during updates. Things will break loudly and can be easily fixed (again, by AI) before shipping. If something does manage to get through, add more tests to cover it for next time.
This actually makes the LLMs better at coding as well. They can verify their own results and iterate with far less manual validation.
This actually makes the LLMs better at coding as well. They can verify their own results and iterate with far less manual validation.