Jack Cheng quoted Adam Wiggins’ Order of Operations for writing code:
- Make it work.
- Make it elegant.
- Make it fast.
- Make it secure.
I disagree. The biggest problem is that this ignores reality: once it works, how likely are you to go back and make it elegant, fast, and secure?
Write good code the first time.
Marco, thank you. I wish everyone had the same understanding of how you should write code, any code. Personally, I don’t think those 4 items should be hirarchal steps, they should be features. Although the first one is kinda stupid, it always has to work. Plus, you can cut back how much time you spend on speed and performance if you plan and/or outline what it is you’re code will accomplish.
Something I’ve always prided myself in doing and evangelizing within SISL, is do it right the first time. I should also...
1. Drink some coffee 2. Say you’ve got it working 3. Figure out a way it might work 4. Fail to get that working 5. Say...
My guess is that Dave and Marco have different ideas of what it means for code to be elegant. To me, elegant code is...
Good code should be written by default as a standard. There’s always room and time later on for improvements, expansion...
I completely agree with Marco.
Charles exalts the merits of Red, Green, Refactor development, which is similar. I think it’s OK to make things work...
first time. Marco, thank you. I wish everyone had the same understanding...any code....
Couldn’t agree more. In the late eighties and early nineties I was producing embedded code for Rolls Royce and Lucas...
Agree with Marco. Usually this approach doesn’t work. The same problem with unit test and javadocs in Java - if you...