2 ms·
It may seem like it, but no engineer writes "right" code on the first try. They get it working, then they iterate, cleaning it up to make it "right". Experienc
by deedubaya 11y ago
It may seem like it, but no engineer writes "right" code on the first try. They get it working, then they iterate, cleaning it up to make it "right".
Experience teaches us where to start, where to think ahead a little, and how to structure code such that it can be refactored in the future.
Writing code the "right way" means 1) getting something working 2)taking what you've learned and refactoring and/or.
If you care about maintaining a chunk of code for 6 months, or a year, you'll quickly learn to refactor. If you are prototyping, right likely isn't a priority to begin with.
- taneq 11y agoThe three priorities of software development: 1) Make it work (at all) 2) Make it work right 3) (If necessary) make it work fast
- pramodliv1 11y agoI heard a similar quote from Nathan Marz of Storm fame: "First make it possible, then make it beautiful, then make it fast" http://nathanmarz.com/blog/suffering-oriented-programming.html http://nathanmarz.com/blog/suffering-oriented-programming.ht...
- mobiuscog 11y agoThe three priorities of software companies: 1) Make it seem to work 2) Ship it 3) Profit ?
- g_delgado14 11y agoBeing self-taught left me with the [false] impression that the reason I don't write good code the first time around is because I never formally studied CS.
- bottled_poe 11y agoI guess that depends on whether you are developing candy crush or a aircraft guidance system. Everything starts with prototyping, but only on low-risk software will engineering procedure be discarded for the sake of 'failing quickly' or being first to market.