I'm so happy I kept on watching after the somewhat long winded start. Such a treat with astonishing depth. Thank you Dave! You made me happy today and I will do my best to pass on the fun
Writing good code is more than correctness and code that anticipates change, it is actually multi-faceted. - Correctness (Pursuit of) - Change - Maintainability - Performance - Security - Re-usability - ... etc So to focus solely on one of these things at the expense of others is foolish. The best solution is to analyze your problem domain and determine which subset of these you want to prioritize, and then lazer focus on those. For example: If you are writing a school project, you may prioritize correctness and re-usability over performance or security. If you are writing code in a startup, you may instead prioritize change, maintainability, reusability, and performance. It just depends on what domain and problem you have at hand. You can't focus on all aspects, so must make sacrifices somewhere to optimally balance them for the problem at hand. However, you should also at least attempt to incorporate at least a little bit of all of them to ensure that your code quality is as high as you can feasibly implement.
Always a pleasure to listen to Pragmatic Dave
I'm so happy I kept on watching after the somewhat long winded start. Such a treat with astonishing depth. Thank you Dave! You made me happy today and I will do my best to pass on the fun
Exceptional! 👏
I was programming in the 1990's and we used waterfall and Structured Analysis and Design and Programming and we DID go back are re-evaluate
ruby Dave since 2007!!
Writing good code is more than correctness and code that anticipates change, it is actually multi-faceted.
- Correctness (Pursuit of)
- Change
- Maintainability
- Performance
- Security
- Re-usability
- ... etc
So to focus solely on one of these things at the expense of others is foolish.
The best solution is to analyze your problem domain and determine which subset of these you want to prioritize, and then lazer focus on those.
For example:
If you are writing a school project, you may prioritize correctness and re-usability over performance or security.
If you are writing code in a startup, you may instead prioritize change, maintainability, reusability, and performance.
It just depends on what domain and problem you have at hand. You can't focus on all aspects, so must make sacrifices somewhere to optimally balance them for the problem at hand.
However, you should also at least attempt to incorporate at least a little bit of all of them to ensure that your code quality is as high as you can feasibly implement.