this post was submitted on 19 Jul 2025
844 points (99.8% liked)
Greentext
6788 readers
1834 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had a coworker who was obsessed with writing unit tests. He was the lead developer on a project which was supposed to take three months and at one point had gone past the two year mark without producing working code. At one point during a meeting with the increasingly (and legitimately) unhappy client, he blurted out "but we've written six times as much test code as actual code!" He was not exaggerating either. Believe it or not, this made the client even less happy.
I think my last programming job (a couple of years ago) had a healthy relationship to tests. You had to do meet a certain coverage percentage, and if you had particularly interesting pieces of code, they should better be tested. But they acknowledged that 100% is just stupid, and that testing the same boilerplate over and over was a waste of time.