Estimating how long it takes to build software – or even how much effort a sprint is – is pretty hard. Estimates often turn out to be too optimistic, and mispredictions can be pretty hard to explain to management. I know why this is so – Michael Wolfe on Quora has a great analogy (there is even an interesting discussion on Reddit), which I agree with. But I'm wondering whether there's an easier analogy.
I was researching career path advice for software developers when I stumbled upon Software Development Career Paths by John Sonmez. It's an excellent blog post. John advises that you make several key decisions (e.g. on what kind of developer you want...
I have not had much luck so far with figuring out what makes a good company purpose. However, I did spend the past few weeks thinking about what Phusion should stand for. One of the topics I have been researching a lot is technology ethics. Technology...
In general, people do not customize their tools or environment. They tend to work with whatever was the initial setup. In this post I will explore the consequences of this phenomenon, which even extends beyond the world of software.
