> I wonder if it's two fundamentally different kinds of personalities at work.
Not two different kinds of personalities, just two different kinds of work. Many people find ways to do both.
The minimalist role is better for learning and building for the art of it — when the purpose of the making is the making itself. The article is a great example of this.
The other role is when that learning needs to be applied to a further end. E.g. when shipping product, code is a "means," and pre-built libraries and layers of abstraction are leverage.
Not two different kinds of personalities, just two different kinds of work. Many people find ways to do both.
The minimalist role is better for learning and building for the art of it — when the purpose of the making is the making itself. The article is a great example of this.
The other role is when that learning needs to be applied to a further end. E.g. when shipping product, code is a "means," and pre-built libraries and layers of abstraction are leverage.