"If you're writing a lot of code to do something, you're probably doing it wrong." - Marco Cantu

Bull fucking shit. This is codecamp level retardation.

This quote requires a lot of context, ironically.

I prefer more code over more libraries. Keep dependencies at a minimum.

@vintprox > "This quote requires a lot of context, ironically"

Context is having a minimalist mindset. Getting things done using as little code as possible. More code=technical debt=pain pain, and more pain.

A good example where I used that quote (and pissed off the dev) was when he wrote his own C# parallel for-each library because he looked at the generated CLI code and said he could do better.

Dev spent a couple of months, wrote contrived tests "proving" his library was faster than Microsoft's, then the day of the release (part of our product data service), it crashed within 5 minutes of real web traffic. Customers were seeing search results of other customers, all kinds of performance and other weird issues.

His code was brilliant, showing a deep understanding of the architecture, but he wrote *a lot* of code he didn't have to.

@PaperTrail Early optimization shouldn't be done.

I code like am making music, half the time while am coding I do not know what am doing but if it keeps working I keep going. I do all optimisations later.

Helps with overengineering and overthinking problems, the problem might be simpler than you think.