Jimmy Koppel: there are two ways to write bad tests—most devs only know one
jimmykoppel · x · 2026-10-19
Jimmy Koppel argues there are two ways to write bad tests, and most programmers only know one: too little testing misses bugs. The less obvious failure mode is tests that check too much, which he elaborates in an attached thread.
More from coding & agent
- Swarms ships v16 'Overclock', claims 53.7k GitHub stars and 800k developers — KyeGomezB · 2026-10-19
- Arvind Narayanan: The question shifts from 'What can AI do?' to 'What should AI do?' — soumitrashukla9 · 2026-10-19
- Dev ports 86Box to WebAssembly with Claude Code: a buildable, breakable retro PC in the browser — No_Twist_678 · 2026-10-19
- Solo dev ships Stillworlds, an 11-world Mac ambient app built with Claude Code, for £5.99 — ninja81702 · 2026-10-19
- Google open-sources Harness2: agents that refine their own harness, up to 11.5-point gains — chemist_slime · 2026-10-19
- Indie dev builds Utsushi, an open-source Higgsfield clone in Go/HTMX — _playlogic_ · 2026-10-19