4 ms·
The most efficient way to do it is to do it once.
by rdiddly 8y ago
The most efficient way to do it is to do it once.
- atoav 8y agoWhich leads to the heart of the discourse: programming is many things at once. Programming a single purpose library or module who has to do one thing and this one thing as good as possible demands efficient and sustainable solutions. Theoretically if you get that kind of code just right, you don’t have to touch it again for a long time. On the other hand you have code where the codes environment is so volatile or ephemeral, that developing the appropriate code isn’t possible, because you are aiming at a moving target. This often demands faster solutions, shims, code that was never really meant to be maintained etc. Sadly many companies have a culture where these shims become like glorified tradition and a few years down the line you have a pile of shims that nobdy sane is willing to touch. However there are situations where fast solutions make sense, e.g. because it is a one time thing or it doesn’t really matter that much etc.
- baddox 8y agoThat is definitely not true for all tasks, and especially not all software engineering tasks.
- blunte 8y agoIndeed, but the prereq is that you know the need absolutely and correctly initially. And you usually don't.