Always write good code.

marco:

Jack Cheng quoted Adam Wiggins’ Order of Operations for writing code:

  1. Make it work.
  2. Make it elegant.
  3. Make it fast.
  4. 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.

Permalink | Comments | March 19th, 2009 at 10:12 am | 11 months ago
  1. iheartmyart reblogged this from jackcheng
  2. eduardoe reblogged this from marco
  3. gurupanguji reblogged this from marco and added:
    Something I’ve always prided myself in doing and evangelizing within SISL, is do it right the first time. I should also...
  4. kodewulf reblogged this from marco
  5. jakeoliver reblogged this from marco and added:
    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...
  6. mcodik reblogged this from caterpillarcowboy and added:
    My guess is that Dave and Marco have different ideas of what it means for code to be elegant. To me, elegant code is...
  7. helloimchris reblogged this from marco and added:
    Good code should be written by default as a standard. There’s always room and time later on for improvements, expansion...
  8. marreka reblogged this from marco and added:
    I completely agree with Marco.
  9. justinday reblogged this from mikehudack and added:
    Charles exalts the merits of Red, Green, Refactor development, which is similar. I think it’s OK to make things work...
  10. rebeltechnica reblogged this from marco
  11. templated reblogged this from marco
  12. sivadcm reblogged this from mikehudack
  13. guillee reblogged this from marco
  14. yasmary reblogged this from marco and added:
    first time. Marco, thank you. I wish everyone had the same understanding...any code....
  15. terryblakey reblogged this from marco and added:
    Couldn’t agree more. In the late eighties and early nineties I was producing embedded code for Rolls Royce and Lucas...
  16. sandlex reblogged this from marco and added:
    Agree with Marco. Usually this approach doesn’t work. The same problem with unit test and javadocs in Java - if you...
  17. mikehudack reblogged this from marco
  18. caterpillarcowboy reblogged this from marco and added:
    I disagree with Marco, unless the problem and solution are already perfectly defined (which is rare). In a world of fast...
  19. caseyliss reblogged this from marco and added:
    Agreed. Part of being an engineer (by education and trade) is balancing trade-offs: code elegance vs. code speed vs. my...
  20. whileyouwereout reblogged this from marco
  21. marco reblogged this from jackcheng and added:
    Jack Cheng quoted Adam Wiggins’...for writing code:...I...
  22. rainbowhill reblogged this from benkraal and added:
    apologise Ben, you’re putting...first couple of steps into practice.
  23. benkraal reblogged this from jackcheng
  24. tungjacob reblogged this from jackcheng
  25. jackcheng posted this