News for hackers. Stuff that matters.
Re:How to Design Software Good by marcosdumay on Friday November 09, 2018 @01:58PM (#18416894)
> General rule: if something only has benefits, it's probably because you didn't figure out the drawbacks yet.

And that, of course, has it's exceptions too. Non-optimized stuff exist, and everything that isn't on the optimum line can be improved in some way without drawbacks. Besides, the optimum line is always moving.

Re:How to Design Software Good by koonsolo on Saturday November 10, 2018 @04:15AM (#18420563)
So you optimized some code, cool!

- How certain are you that you didn't introduce a bug? - Is it also running faster on this exotic platform that we still need to support? - Did it involve API changes? - Do we need to put this into production now, or wait for the next optimization to save some time? - How much time did we spend on this? Was there something else that would have made a bigger impact?

In theory you can improve things without drawbacks, but in practice you always have to make the right trade-offs.

Re:How to Design Software Good by marcosdumay on Saturday November 10, 2018 @12:14PM (#18422225)
Just to point, my comment wasn't about code optimization (but can apply to it too).