The premise that the cost of change increases exponentially as the project goes on has dominated engineering disciplines, which surfaced the necessity of upfront design. Is that the case for software?
I often make the mistake of holding too strongly to my opinions. I will try to
keep this list up-to-date as tribute to those moments.
The list is sadly trivial and short. I could definitely use help remembering
more events. Do reach out if you ever caught me being wrong in
I am in the process of deleting my presence on the last social networking
website I have left, LinkedIn. This has
been triggered by their latest
In no particular order.
Listening to podcasts. I’m very fond of podcasts. Having something interesting to listen to all the time has gotten me to walk more, do more dishes, and enjoy an otherwise bad commute (remember those?) Plus, like any new medium, it feels like a close community: there are so many creators I feel very close to. Many years in, however, the downsides are very clear: constant craving for novelty and entertainment, mindlessness, reluctance to connect to people nearby (the few people who are not wearing headphones anyway.
After re-reading some of the papers from Bell Labs, something clicked in my
mind, and I’m hooked. I’m now reading “The UNIX Programming
by Kernighan and Pike. It’s got that fun style you’re probably familiar with, if
you’ve read K&R or the blue book. One of the first exercise
questions, on the chapter on file systems: