3 ms·
Life is too short to poorly build a house, a house that will break down, with the windows and doors in the wrong place. Likewise, life is too short to write po
by jll29 4y ago
Life is too short to poorly build a house, a house that will break down, with the windows and doors in the wrong place.
Likewise, life is too short to write poor code. Either you already know from the outside it's going to be used, or you don't think it is going to be used and life surprises you. In both cases, you will want to have written good code. Only the edge case of 0 users is compatible with poor code, and that is perhaps code that should not be written at all, because your time is limited on earth.
Exception: code to learn.
N.B.: There is beautiful code written by single people (e.g. SQLite, REDIS, Dave Hanson's LCC compiler and his beautiful "C: Interfaces and Applications" library [1], Stanford GraphBase) and ugly code written by groups (not giving examples here not to offend folks - some of it is also still very useful, and used by me!).
[1] https://drh.github.io/cii/ https://drh.github.io/cii/
- jdthedisciple 4y agoNot to speak against good code but I'm pretty sure users don't care about the code. Just look at the famous Nomadlist story. Maybe you meant the edge case of 0 co-developers, which in reality isn't so much of an edge case. Imho it's all about cutting edges at the right places and making educated compromises.