you can;t even IMAGINE what it is


I think about "craft" a lot. I think about it as a knockon effect of learning about early industrialization and the purpose of mechanization in industry (which is to reduce the skill floor to make workers more interchangeable).

And I think about coding boot camps, too. And I think about the proliferation of microservices and libraries that get glued together.

And I think about the Masters of Fine Arts in Software Engineering. It seems so elegant, and it seems like it dovetails into what I try and do as a profession.

I don't like thinking of software as an "engineering" kind of job. I think that causes so many issues. Because it's never just engineering, is it? It's design - its a kind of art. An engineer doesn't need to consider the interface for a bridge or a transformer or an elevator hoist. These things don't have interfaces. Every piece of software has an interface, even libraries, even short little scripts.

There aren't, and shouldn't be, simple static-load-analysis answers in software. There just cannot be. It betrays the user and insults them. Doing software well is a craft. Beautiful work is recognizable.


You must log in to comment.