Post

IMO, software devs have long had a cultural undercurrent of self-perception as *artisans* doing highly-detailed small batch or bespoke work, which is both wrong as a matter of primary economic context and sets up the adherents for a bad mismatch with AI's utility for software engineering.

Personally I always tried to be a software artisan doing highly detailed well done work, and I'm trying and will try to do the same with AI… A friend posted yesterday something like "you do you, but for me the product is better when you love your craft" and it bugged me because I *do* love my craft

I don't think artisans exclusively own the idea of doing good work. Rather, artisinal work is distinguished by being in some manner un-scalable. A bespoke suit is valuable both because it is tailor-made for the individual customer *and* because the buyer places value on work done by hand.

0 reposts16 likes

That's a valid choice, and there are valid businesses that work in that manner! But it's not the primary economic mode of software development, and in fact it's not clear to me you can make a software business that is "handmade" (and fetches premium or luxury prices to compensate).

I think instead many software developers have gotten away with acting as artisans within an enterprise because even production-level software work is historically slow and labor-intensive, and so the slowness of an artisan was within an often-acceptable bound in an enterprise.

Yeah, that's fair! It's absolutely a space where programmers who don't want to be bound by the limits of the enterprise have tried to construct alternative modes of engaging with capital! I wonder if OSS would exist or be as big if it were easier/possible to sell artisinal and/or luxury software.

That bound is blown away when automation suddenly drives up the productivity of a "regular" (non-artisinal) software developer in an enterprise. Suddenly, folks committed to being artisans in an enterprise are very obviously less productive than their peers.