This is the second post in a series of advanced technical topics. In the previous post, we discussed idempotence, the idea that some code must be written such that it can be run multiple times with the same inputs and deliver the same results and side effects. The post was running a little long, though, […]

A couple of years back, I ran a series of posts which tried to explain what it meant to achieve mastery in software engineering, including a tongue-in-cheek answer to the question of what it meant to work on hard problems. But looking back, none of these really answered the question of what kinds of hard […]