Lots of code is write-once, and in that situation productivity at the cost of technical debt is absolutely the right decision. There's no easy right answer.
I disagree. It doesn't take any real time to write a comment while you're thinking of it; coding for work is not a speed contest where seconds count, and if you're trying to save 60 seconds not writing comments, you're doing something wrong.
Most likely, people who don't comment have the exact same mentality you have ("this is write-once, no one's going to look at it"), but the problem is they're wrong. Other people do come back and need to change it later.
