3 ms·
"I've seen too many of my previous projects die right when I moved on. Now I tend to write code as if it were written by a beginner: verbose and boring, with no
by hutzlibu 6y ago
"I've seen too many of my previous projects die right when I moved on. Now I tend to write code as if it were written by a beginner: verbose and boring, with no magic."
Theres nothing wrong with charming magic in your code, if it really does something special and is not just used for the sake of it - it only gets into dark magic, when you forget or are too lazy to add proper documentation in the end.
Which ... happened to me, too many times.
But otherwise very much yes. Clarity and simplicity should be always goal number one. But since simplicity is hard to reach at times and time is short, it is always about the balance.
- bigbizisverywyz 6y agoI once read a quote, possibly here on HN that said: "Code first for the machines, then for others that will maintain your code and lastly for yourself." And that I think for me nicely strikes the balance.
- hutzlibu 6y agoHm, coding for the machine would mean to me, write processoroptimized code allways. And I rather have clear, maintainable code - which is easier to work with and therefore less filled with bugs.