zlacker

>>tablet+(OP)
> "For art, music, and writing? I got nothing. I’m inclined to believe the skeptics in those fields."

You've already lost me, because I view programming as an art form. I would no more use AI to generate code than I would use it to paint my canvas.

I think the rest of the article is informative. It made me want to try some things. But it's written from the perspective of a CEO thinking all his developers are just salt miners; miners go into the cave and code comes out.

I think that's actually what my hangup is. It's the old adage of programmers simply "copying and pasting from stack overflow" but taken to the extreme. It's the reduction of my art into mindless labor.

>>TheCra+U3
Woodworking is also an art form. But most people just need furniture, fixtures, and structures. Nobody would take seriously the idea that new construction all be done with sashimono joinery in order to preserve the art form, but somehow we're meant to take seriously the idea of hand-dovetailed CRUD apps.

>>tptace+o4
> Woodworking is also an art form. But most people just need furniture, fixtures, and structures. Nobody would take seriously the idea that new construction all be done with sashimono joinery in order to preserve the art form, but somehow we're meant to take seriously the idea of hand-dovetailed CRUD apps.

How many furniture makers did you talk to forming this opinion? The metaphor does not line up with either my software of furniture experience. I work with production furniture shops that choose not to use CNCs to avoid the soul being sucked out of the work. This is not a rare stance to take and this is not "japanese joinery" woodworking. This is real work, balancing the means of production with optimal quality. There is all sorts of arguments on whether cncs or using a domino or whatever is "real" woodworking, but the idea that this choice of quality does not exist in woodworking and so we shouldn't have it in software is not my experience.

>>bradly+sq
You don't need to talk to furniture makers to know that mass produced furniture has replaced cabinetmakery almost completely. Most of us are sitting on the evidence.

>>pvg+Sw
It is not about being mass produced or not–it is this reoccurring theme by people who do not spend their days writing code saying that mediocre code is good enough. It is not for me. Code decays. Mediocre code today is bade code tomorrow. Not everyone shares this pov–totally fine–but the tone of the article is tough.

>>bradly+Kz
Right but just like most people were looking for a cheap shirt, pot or chair, most people are looking for 'cheaper way to make computers do what I want'. These changes didn't happen because people hated art or failed to inquire with weavers, potters and joiners.

>>pvg+bA
But woodworkers still woodwork just fine with mass production. Just there are mass produced things. And there are not. So then there can be mass-produced code and there can not be. The article feel all or none and I do not think that translate to woodworking or software.

>>bradly+lD
I don't think the article says that. People still write games for the NES in assembly but that's effectively unrelated to current software development practice.

>>pvg+gE
Again, this comparison that professional woodworking is anything like NES game building is just so far from my experience. Cabinet makers (and to a less extent furniture makers) are numerous and very successful.

Mass production doesn't have to eliminate the alternative to exist. The same way fast-food and cheap groceries are not a threat to quality restaurants.

>>bradly+XA1
This 'only one can exist' is something you brought in, though. Neither the article nor I am saying that.