The vast majority of coding isn’t making something new, it’s using existing patterns and tools and arranging them to fit a specific use case.

I would argue that arranging something to fit a specific use case is making something new.

Ask any designer how difficult it is to get a spec sheet from a client and meet their expectations. We're expecting LLMs to suddenly solve this problem.

Llms may not be able to create a new framework or design pattern

Until they can do this, there is little threat to designers. There will be less grunt work, of course.

Tbh this whole thing made me realize what we really need is a modular automated code bank. There's so much duplication of effort it's honestly absurd.

Right we've got this scattershot network of libraries but no one's really been up to the task of taking the next logical steps.

Right now they are. Who knows what tomorrow will bring?

We do. Experienced programmers who have been promised we're about to be obsolete several times, now. For many of us, this isn't our first rodeo.

As an expert in computers, there's two things I can guarantee about the future of computers:

1. Computers will just keep getting smarter.
2. After decades of getting smarter, computers remain deeply stupid in ways that non-experts cannot imagine. However dumb you think your computer might be, I promise it's somehow significantly dumber than that.

No, it's the difference between software engineering and software development. If your project manager is handling that, your org is wack

If you're not understanding why the spec is the way it is, you're just creating job security for your replacement lol

I thought that was just the job we give people who are trying their best but can’t really anything.