✳flâneur — a map of the web's best reading

Thing worth doing

okigiveup.net · 1,158 words · saved by 1 readers

At last, I managed to make it through “Art of Unix Programming” by Eric Raymond, thanks to a long train ride and an extended weekend. It’s a very relevant book for all kinds of programming work, despite the rather exclusive title, and I will make a post about it soon (the draft is ready, still working on it), but one of the central themes mentioned as a part of the Unix philosophy connected really nicely to something else I was preoccupied with for a while now. Among the “supreme principles” of the Unix methodology, there is a principle called “Rule of Optimization”, which is that a programmer should “Prototype before polishing, get it working before you optimize it”. When you start working on a software project, it is difficult to know beforehand which parts of it are going to be difficult to write or decisive for the architecture of your code. Instead of relying on preconceived notions and prematurely spending unnecessary amounts of time to get the perfect design or the fastest algor

At last, I managed to make it through "Art of Unix Programming" by Eric Raymond, thanks to a long train ride and an extended weekend. It's a very relevant book for all kinds of programming work, despite the rather exclusive title, and I will make a post about it soon (the draft is ready, still working on it), but one of the central themes mentioned as a part of the Unix philosophy connected really nicely to something else I was preoccupied with for a while now. Among the "supreme principles" of the Unix methodology, there is a principle called "Rule of Optimization", which is that a programmer

Explore this link on the map →

related reading