Mike Hudack

Write bad code now, improve it later?

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? If it’s for personal use, how likely are you to care? If it’s for work, how likely is your employer to be willing to devote resources to “clean up” something that already works? Even the best developers, and the best employers, are pretty bad at this.

You should be writing elegant code very early in the process. There’s always room for improvement, of course, but there’s never an excuse to write sloppy code, even if it’s only running once and you’re the only person ever seeing it.

“Make it fast” can arguably be a lower priority for simple optimizations and constant-time reductions. But algorithmic complexity needs to be considered from the beginning.

And saving “Make it secure” for last seems like a disaster. Imagine how you’d feel, and how you’d even begin to tackle this problem, if someone handed you a pile of another programmer’s code and said, “Make this secure.”

Write good code the first time.

reblogged from marco

1. shiu liked this
2. owen liked this
3. planetelex liked this
4. notentirely liked this
5. philish liked this
6. iheartmyart reblogged this from jackcheng
7. ruminator liked this
8. eduardoe reblogged this from marco
9. mies liked this
10. 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...

11. soxiam liked this
12. athertonbartelby liked this
13. ninakix liked this
14. ericalba liked this
15. pmcarthur liked this
16. caseypugh liked this
17. jameshull liked this
18. kodewulf reblogged this from marco
19. yesongaymarriage liked this
20. tedroden liked this
21. designage liked this
22. 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...

23. 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...

24. nicolasgut liked this
25. andybons liked this
26. morningstar liked this
27. deadlybrad42 liked this
28. 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...

29. marreka reblogged this from marco and added:

    I completely agree with Marco.

30. brainofg liked this
31. madamex liked this
32. 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...

33. rebeltechnica reblogged this from marco
34. mojaam liked this
35. templated reblogged this from marco
36. berezina liked this
37. mokoyfman liked this
38. sivadcm reblogged this from mikehudack
39. ragdoll liked this
40. bewuethr liked this
41. guillee reblogged this from marco
42. 2arrs2ells liked this
43. reallyreallybig liked this
44. hammocknotes liked this
45. yasmary reblogged this from marco and added:

    first time. Marco, thank you. I wish everyone had the same understanding...any code....

46. 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...

47. onigiri liked this
48. joshkinberg liked this
49. mikehudack reblogged this from marco
50. squashed liked this
51. hermzz liked this
52. trey liked this
53. 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...

54. 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...

55. danriti liked this
56. whileyouwereout reblogged this from marco
57. inky liked this
58. wezzo liked this
59. marco reblogged this from jackcheng and added:

    Jack Cheng quoted Adam Wiggins’...for writing code:...I...

60. jratlee liked this
61. rainbowhill reblogged this from benkraal and added:

    apologise Ben, you’re putting...first couple of steps into practice.

62. benkraal reblogged this from jackcheng
63. tungjacob reblogged this from jackcheng
64. jackcheng posted this