3 ms·
>Best practices can slow your application down Yes, but they will do it in an elegant manner and be sanctioned by lots of self appointed experts. Where would
by DeathArrow 5y ago
>Best practices can slow your application down
Yes, but they will do it in an elegant manner and be sanctioned by lots of self appointed experts.
Where would us be today without the wisdom of Uncle Bob and Gang of Four? We would be still in the prehistory of programming writing efficient, inelegant code.
- danuker 5y agoIt depends on the application. You have to balance the costs of writing efficient code with the costs of running the machines. If you have lots of users hitting your servers, it's worth investing more in efficiency, but if you barely have any, it's much more worth it to write in a convention focusing on maintainability.
- kaba0 5y agoThere are entirely different problem domains inside software engineering. Pushing that last bit of performance at the price of some maintainability can be the sane choice for some numerical optimization/simulation algorithm for example, but would be a terrible choice for a bank application dealing with transactions and having often changing requirements. At the latter, even serious inefficiencies are absolutely worth it. Hardware is relatively cheap and really fast. Also, don’t forget that we are trying to balance at the top of the often non-reducable complexity mountains, never ever seen before. Compared to some of the programs out there, going to the moon is just some trivial computations. The former may very well not be remotely possible without some structure for our limited human brains.