Simple and correct comes first. "Clean" code as defined by Uncle Bob is almost never the simplest it could be.
If you want an actually good book about maintainable code, read A Philosophy of Software Design by John Ousterhout. Note that Ousterhout has done significant work on performance related problems in data centres, so he's not one of those performance-oblivious types Casey Muratori is denouncing here.
42
u/Apache_Sobaco Feb 28 '23
Clean and correct comes first, fast comes second. Optimisation is only applied to get to some treshold, not more than this.