Re:Interruptions cost 23 minutes 15 seconds, right?
by cookiengineer on Sunday August 24, 2025 @12:04AM
(#45001283)
For me the deciding factor was whether or not I had tests available for that task to get right back into it.
If I don't have tests available, I always need to re-read so much code that it feels like having to start all over again to be able to get a mental picture of the complexity.
I started to love Go for that very reason, because I always have my state written down in the form of unit tests while I am implementing it. This removes so much burden of thought after I got interrupted, because all edge cases I can write down and I don't have to actively try to remember them. Go made me fall in love with Test Driven Development, again.
If I don't have tests available, I always need to re-read so much code that it feels like having to start all over again to be able to get a mental picture of the complexity.
I started to love Go for that very reason, because I always have my state written down in the form of unit tests while I am implementing it. This removes so much burden of thought after I got interrupted, because all edge cases I can write down and I don't have to actively try to remember them. Go made me fall in love with Test Driven Development, again.