News for hackers. Stuff that matters.
Re:I'm a good engineer but I suck at building stuff by ogreveins on Tuesday May 10, 2016 @02:58PM (#11669633)
Here's a priority list that you should typically follow for making anything.

1. Make it work.

2. Make it not break.

3. Make it fast.

That's it really. Until the performance of something is blocking what you need to do somewhere else leave it the hell alone.

Re:I'm a good engineer but I suck at building stuff by rednab on Tuesday May 10, 2016 @04:10PM (#11670254)
Per (as far as I can tell) the original: http://c2.com/cgi/wiki?MakeItWorkMakeItRightMakeItFast

1. Make it work.

2. Make it right.

3. Make it fast.

Re:I'm a good engineer but I suck at building stuff by ogreveins on Tuesday May 10, 2016 @05:35PM (#11670863)
Wow, I honestly never read that. +1 for the link, I love old stuff like this.
Re:I'm a good engineer but I suck at building stuff by nickpsecurity on Tuesday May 10, 2016 @07:55PM (#11671652)
c2 is a great wiki. Start googling languages and programming phrases with site:c2.com at beginning. You'll find some good stuff. Unfortunately, its commenting got shut down shortly after I discovered it. I think I read all the debates and stuff. Too many haha.

Note: The debates over LISP, OOP, Cleanroom, Smalltalk, and so on are all especially interesting.

Re:I'm a good engineer but I suck at building stuff by gohrt on Tuesday May 10, 2016 @07:14PM (#11671423)
Make it run, right, rapidly.
Re:I'm a good engineer but I suck at building stuff by nickpsecurity on Tuesday May 10, 2016 @07:58PM (#11671670)
Butler Lampson

http://research.microsoft.com/en-us/um/people/blampson/33-hi...

Unfortunately, his current employer chose a different order: 3, 1, 2. Sometimes they drop 1, 2, or 3 separately or in groups at random. Gotten much better at 2 and 3, though.

Re:I'm a good engineer but I suck at building stuff by koolba on Tuesday May 10, 2016 @03:17PM (#11669796)
4. Throw it away and rebuild it now that you know how it really should work.
Re:I'm a good engineer but I suck at building stuff by 6stringmerc on Tuesday May 10, 2016 @03:32PM (#11669917)
In some cases this is excellent advice regarding a story or essay re-write as well.
Re:I'm a good engineer but I suck at building stuff by firebones on Tuesday May 10, 2016 @10:56PM (#11672370)
Your coda is often forgotten, and sometimes "Make it Fast" is essential to making it work.

[1] http://c2.com/cgi/wiki?DesignForPerformance

Re:I'm a good engineer but I suck at building stuff by danieltillett on Tuesday May 10, 2016 @04:10PM (#11670247)
1. Make it work.

2. Ship it before your competitor does.

Re:I'm a good engineer but I suck at building stuff by reefoctopus on Tuesday May 10, 2016 @03:04PM (#11669674)
4. Make it manageable.
Re:I'm a good engineer but I suck at building stuff by ianstormtaylor on Tuesday May 10, 2016 @03:12PM (#11669745)
I'd probably swap them:

1. Make it work.

2. Make it not break.

3. Make it manageable.

4. Make it fast.

Otherwise I find that trying to make something fast before making it manageable usually ends up in crazy hacks that are hard to undo later.

Re:I'm a good engineer but I suck at building stuff by stevetrewick on Tuesday May 10, 2016 @03:19PM (#11669810)
3.5 Profile it to see whether or not it needs to be faster
Re:I'm a good engineer but I suck at building stuff by voltagex_ on Tuesday May 10, 2016 @09:26PM (#11672012)
If you profile it on a fast machine, your results might lie to you.
Re:I'm a good engineer but I suck at building stuff by douche on Tuesday May 10, 2016 @09:53PM (#11672121)
Or on a machine on a fast network, or SSD vs spinning-rust, or any number of varying factors.
Re:I'm a good engineer but I suck at building stuff by ogreveins on Tuesday May 10, 2016 @03:18PM (#11669799)
I'd agree with this. My last couple of projects did have a couple of hacks that bordered on spaghetti code until they were sufficiently cleaned up.
Re:I'm a good engineer but I suck at building stuff by gohrt on Tuesday May 10, 2016 @07:14PM (#11671429)
It's less likely to break if it's manageable first.
Re:I'm a good engineer but I suck at building stuff by billylindeman on Tuesday May 10, 2016 @07:20PM (#11671458)
In hardware dev I've followed a similar paradigm from an old mentor:

1) Make it work

2) Make it work better

3) Make it work cheap

Re:I'm a good engineer but I suck at building stuff by blakeyrat on Tuesday May 10, 2016 @04:38PM (#11670477)
Make it USABLE. USABLE. Study its USABILITY.

The world doesn't need more crummy unusable software.

Re:I'm a good engineer but I suck at building stuff by siliconc0w on Tuesday May 10, 2016 @11:53PM (#11672543)
I use crummy unusable software all the time because it's good.
Re:I'm a good engineer but I suck at building stuff by eterm on Tuesday May 10, 2016 @04:03PM (#11670196)
I've seen that as:

1. Make it

2. Make it work

3. Make it fast