[S201]

> Folks still enjoy doing woodworking and make boxes, tables, benches, etc. -- even though they could easily buy them new, used, or for pretty cheap (say, at IKEA).

For what it's worth, many woodworkers prefer making their own stuff because it is of far higher quality than what you can buy at IKEA (and similar stores). With the exception of extremely high end and expensive stuff, most furniture is complete junk. Making a coffee table out of a solid slab of walnut, for example, will last a lifetime compared to the cheap MDF table at IKEA.

Obviously I nor anyone else can predict the future, but I wouldn't be surprised for a similar divide to appear with AI generated software vs. completely hand written software where the hand written software is of higher quality for those that desire such things.

[shon]

I disagree with the idea that handwritten software falls into the same category has handmade woodworking. Unlike software, there is no machine that can do the type of woodworking you describe.

At least for now, we still have the unsolved 'robotics problem' where the data to train humanoid robots to do woodworking better than a human doesn't exist in sufficient quantity to make it work using current AI training techniques. This too may soon change via synthetic training data or some modified technique.

Conversely, my own experience shows that even with context window limitations, ChatGPT is already better than 90% of working software engineers for generating small practical programs. Here's why it's better:

1. It's better because it not only knows how to code but is equally knowledgeable about product management, UI design, business practices, etc which makes it more like interacting with an 'architect level' engineer 2. It knows a good if not 'the best' way to do most things

[JohnFen]

> ChatGPT is already better than 90% of working software engineers for generating small practical programs.

Not sure how you measure this. However, if by "small practical programs" you mean "trivial programs", then I see no reason to doubt your assertion.

That said, at least where I work, ChatGPT hasn't been a real benefit for real work. By the time you manage to craft the right prompts, then check and correct the code produced, then incorporate it into the larger project, it all takes a bit more time and effort than if you just wrote it yourself in the first place.

[shon]

100% John, I do mean trivial programs.

It’s the stuff that you should not bother an engineer to do, but it can’t be done (in a reasonable timeframe) by a business person or even a technical IT person who isn’t proficient at code.

There’s a space there, a practical need for things that are boring or obnoxious for an actual SWE but that fill some business need or use case. ChatGPT fills these in nicely.

[S201]

> Unlike software, there is no machine that can do the type of woodworking you describe.

A CNC?

> Conversely, my own experience shows that even with context window limitations, ChatGPT is already better than 90% of working software engineers for generating small practical programs.

Well if we're doing anecdotal experiences, I find ChatGPT (both with 3.5 and 4) useful for replacing quick search queries to look up documentation but for anything more complex than that and it quickly starts making up blatantly incorrect examples even for small programs making it more than useless most of the time for me at least. But you're welcome to disagree; I don't have the energy anymore to get into my 1000th internet discussion full of anecdotal evidence trying to validate the future merits of generative AI for software engineering purposes.

[shon]

> Making a coffee table out of a solid slab of walnut, for example, will last a lifetime

Not CNC, right?

Yeah I think it's fun to discuss. I think we're saying the same thing. I'm not saying ChatGPT could replace a professional software engineer for most things at this stage. That clearly isn't practical yet.

As you said, it does make mistakes, though it can often correct them if the context window is there. The differences in how we use it for programming tasks and what we find useful is probably related to our SWE skill levels. Yours is likely much higher than mine, as I've never been a professional SWE.

That said, for the many little automation tasks that business people often bug a real engineer for, like iterating through a CSV and hitting an API to do something, then writing a result, it's ability to write simple and useful python scripts has been amazing for me.

I believe it's getting close to the place where I could use to to prototype simple MVPs but it failed during my last attempt.

[Ferret7446]

> Making a coffee table out of a solid slab of walnut, for example, will last a lifetime compared to the cheap MDF table at IKEA.

It probably costs roughly the same as those cheap tables in terms of materials costs and time/labor/skill. I doubt many if any people are doing it if they hate woodworking; meaning the cost/quality does not justify it.

[S201]

A hardwood table does not cost remotely the same in terms of materials or labor as a cheap table that you can buy at the likes of IKEA and crowd. Hardwood, especially nice hardwood, costs FAR more than MDF. For example, a slab of black walnut sized for a coffee table can be hundreds or thousands of dollars and must be custom sourced from specialty locations or local individuals whereas a 4x8' sheet of MDF can bought at any lumber yard for under $100. And that's not even getting into the difficulty of working with rough cut wood as opposed to S4S wood that you buy at a lumber yard.

[Ferret7446]

Sorry, I meant over a lifetime of ownership+replacement. You'd have to replace the IKEA table more often but it's a lot cheaper. Also, I don't deny that a hardwood table may even cost more over a lifetime, hence why very few people have/buy/make them now given the overall cost/value proposition