the best spec you can give a coding agent is a failing test.
it can argue with a paragraph. it can't argue with red
it can argue with a paragraph. it can't argue with red
Oct 23, 2026 · 12:13 PM UTC
3
0
2
40
@dng_notes Agreed, and keep it small. One failing test per behaviour beats one big red end-to-end test, because the agent can tell which change fixed what. In Java I give the JUnit test a descriptive name, so the name doubles as the spec line in the commit message.
1
0
0
6
@gagu_sh one test per behaviour makes sense. one big red e2e just tells it something somewhere is wrong. test name as the commit line is neat
1
0
1
31
