3 ms·
I don't agree with this article. To me, clean and concise code is a skill that you should work to improve. When you have to solve difficult problems, that skill
by jasfi 3y ago
I don't agree with this article. To me, clean and concise code is a skill that you should work to improve. When you have to solve difficult problems, that skill should be automatic and improve the entire process.
- oweiler 3y agoThat clearly depends on the context. If you want to win a contract, having a functional prototype to be the deciding edge over your competitors. Here, speed of implementation trumps everything.
- jasfi 3y agoThere's no need to sacrifice clean and correct code, the speed of implementation shouldn't be any less. I can understand performing fewer tests in that context, because writing tests can take a lot of time. Still, a minimum number of tests that target complex code is a good idea.
- zimpenfish 3y ago> To me, clean and concise code is a skill that you should work to improve. And he agrees with you - "[... if] what you really want to be is a software engineer".
- jasfi 3y ago> and not the designer of an experience. You can still be the designer of an experience, is what I'm saying. There shouldn't be anything lost if writing code properly is what you always do.