You will never “fix it later”
While the author may never go back and fix his code later, that doesn’t mean that everybody else does the same.<p>If you never have to come back to “fix it”, was it actually wrong to begin with?<p>Personally, in my own career, I’ve found this “come correct” mindset is used to justify unnecessarily flexible solutions to allow for easier changes in the future … changes that 90% of the time, never actually materialize.<p>I held this mindset too when I was younger. Then I got tired of seeing how all my clever abstractions never actually got used the way I intended, and decided to get smarter about it.