News for hackers. Stuff that matters.
Re:Simple, correct, fast: in that order by silverbax88 on Monday July 09, 2018 @11:41AM (#17491046)
I agree. What he means is, it should work first, as simply as possible. Then you worry about correctness- correctness is not referring to working/no working. Correctness means, 'how SHOULD this work?' or 'How should this logic or code be written to be most efficient or effective?'

Third is performance.

1. Write a working piece of software that does the job.

2. Refactor to make the working piece of software do the job more efficiently and elegantly.

3. Refactor to make the working piece of software do the job as fast as possible.

There are no comments on this comment yet.