News for hackers. Stuff that matters.

felixasher

Re:Ask HN: When tests keep passing but design stops moving on Saturday January 17, 2026 @09:01AM (#46658126)
“Cold guardrail” resonates. I’ve been running guardrails only at slice boundaries as well. Deciding when interruption is justified has been surprisingly non-trivial.
Re:Ask HN: When tests keep passing but design stops moving on Tuesday January 06, 2026 @05:25PM (#46519700)
Yes — that framing resonates a lot.

That shift from “does this work?” to “what breaks if this assumption is wrong?” is very close to what I’ve been circling around.

For me, the stall seems to happen when green tests stop reducing doubt and start just confirming structure. Integration-level tests sometimes help me reintroduce that pressure.

Really appreciate you articulating it so clearly.

Re:Ask HN: When tests keep passing but design stops moving on Tuesday January 06, 2026 @05:25PM (#46519695)
Thanks — that’s a fair question, and probably on me for not being clear.

I’m not trying to replace design work with tests. What I’m experimenting with is using certain tests (especially integration-level ones) as a way to surface and challenge assumptions that feel stable on paper.

In other words, the tests aren’t the design, but they’re sometimes the fastest way I’ve found to discover where my “separate design step” was incomplete or misleading.

Happy to clarify more if helpful.

Ask HN: When tests keep passing but design stops moving

I’ve been practicing TDD for a while, and I keep running into the same uncomfortable moment.Tests pass. Coverage improves. Refactoring feels safe.But at some point, the design just… stops moving.Not because the system is “done,” but because the tests no longer seem to challenge anything. They mostly confirm decisions that already feel locked in.I don’t have a clean explanation for this. What I...

( Read More... | 6 comments | on HN )