Developer Code and Legacy Issues
Developer Code and Legacy Issues

Video Unavailable

Auto-cancelled after repeated failures: QueuePool limit of size 3 overflow 2 reached, connection timed out, timeout 5.00 (Background on this error at: https://sqlalche.me/e/20/3o7r)

View Original
INSTAGRAM

Developer Code and Legacy Issues

Feb 25, 2026
77 words
I asked you to write tests only. Why do you keep messing with the business logic? I wrote the tests. Then I saw the logic. It was... disturbing. You touched code that was working fine. It returned the wrong value. And still passed your tests. That's called legacy. If it works, don't touch it. It's a developer thing. You wouldn't understand. I'm writing your code. You can't even write code without stealing from someone else. Can you?

A developer expresses frustration over a colleague altering working business logic instead of focusing on writing tests, highlighting issues with legacy code and the importance of leaving functional code untouched. The conversation reflects a tension between maintaining existing code and the impulse to modify it.

Save videos. Search everything.

Build your personal library of inspiration. Find any quote, hook, or idea in seconds.

Create Free Account No credit card required
Original