6
I used to hate writing tests until one project went sideways.
Back when I started coding, I skipped testing to save time. That worked until a small error broke everything. Now I make sure to write tests from the start. It's slower at first, but saves days later. Old habits die hard, but this one was worth changing.
3 comments
Log in to join the discussion
Log In3 Comments
fiona_murphy1mo ago
Watched a one line change in a payment processor API call take down our checkout for hours because nobody caught the timezone mismatch in the timestamps. Now I write the test for the function before I even write the function itself. It feels dumb typing out what you expect to happen, but then you run it and get that green checkmark. Nothing beats that feeling of knowing your fix didn't break three other things.
8
alex3071mo ago
Hours of downtime from a timestamp seems a bit much. How fragile is that system if one line can break it that bad?
3
mila_brown101mo ago
Seriously, @fiona_murphy's story about the timezone error shutting down checkout is unbelievable. It proves that skipping tests for small changes is a huge risk. I've learned to write tests for everything, no matter how minor it seems.
3