Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance. So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it. craftsoftware
Senior craftsperson A Fragment by Wilson Miner staff.design The thing that you’re talking about though, which I’ve never seen a mature company really have a sustainable space for, is the “senior craftsperson.” They’re not pivoting at some point in their career to saying “I’m going to take what I know and leverage it through other people.” They’re saying “I want to get better infinitely at the thing that I do.” I believe that that’s possible. You see it more in pure-art kind of careers. Like “I’m an illustrator” or “I’m a concept artist” or something, and there’s a need for that person being really fucking good at that one thing, and continuing to do that one thing. I think a lot of people can intuitively understand why that would be really satisfying for someone as a career path. The dual ladder craftwork