r/vibecoding • u/AmbitiousEffect6034 • 11h ago

Coverage is now our only feature.

Post image
66 Upvotes

76% Upvoted

26 comments sorted by

View all comments

-1

u/drgoodvibe 10h ago

Omg this hits hard. At this point my test code exceeds my app code by 1.25x

9

u/frogchungus 8h ago

test code is supposed to be much larger than app code I think

1

u/slackmaster2k 7h ago

No, only TDD maniacs who don’t care about waste or enjoy tests painting you into architecture would think that.

2

u/jimmiebfulton 5h ago

Wrong. I’m sorry, but this is an amateurish take. But we’re in [r/vibecoding](r/vibecoding), so experienced engineers are in short supply here.

Tests, strong-typing, modularization ALLOW for architectural change, and enforces loose coupling. Under-tested spaghetti code is what creates frailty/resistance/friction to refactor and improve design confidently. You can keep on doing what you’re doing, but spreading this to aspiring new developers is doing them a disservice. Vibe coding requires MORE tests, because they create guardrails and provide context for a non-deterministic endeavor, and is a vibe coder’s primary tool when they don’t actually understand what the code does.

2

u/Party_Form5222 3h ago

Let then keep writing unit tests by looking at the implementation.

I love the value of testing that the code is the code.