Jack Cheng's collection of things to remember. For deeper insights, visit jackcheng.com
“ 1. Make it work.
2. Make it elegant.
3. Make it fast.
4. Make it secure. ”
Key take-away: Creating iteratively, and focusing on function instead...form first will...
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...
I disagree with Marco, unless the problem and solution are already perfectly defined (which is rare). In a world of fast...
Agreed. Part of being an engineer (by education and trade) is balancing trade-offs: code elegance vs. code speed vs. my...
Jack Cheng quoted Adam Wiggins’...for writing code:...I...
apologise Ben, you’re putting...first couple of steps into practice.