The benefits code quality gets you is better maintainability, and you don't have to maintain something that won't exist in 12 months. But having said that, you can definitely swing too far in the other direction. There are lots of measures that improve both code quality and reduce time to production. Writing lots of smaller things vs. fewer bigger things, and testing the most crucial parts of the codebase for example.
Good point on smaller vs. bigger. And +1 on testing - I think "it has decent test coverage" is my #3 after 1. "it works" and 2. " it offers good UX." My code is almost always broken in subtle ways if I don't write a test.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Amen brother.
The benefits code quality gets you is better maintainability, and you don't have to maintain something that won't exist in 12 months. But having said that, you can definitely swing too far in the other direction. There are lots of measures that improve both code quality and reduce time to production. Writing lots of smaller things vs. fewer bigger things, and testing the most crucial parts of the codebase for example.
You can favor speed without favoring haste.
Good point on smaller vs. bigger. And +1 on testing - I think "it has decent test coverage" is my #3 after 1. "it works" and 2. " it offers good UX." My code is almost always broken in subtle ways if I don't write a test.