One of my coworkers (not a developer, but familiar enough with technology) asked about a new “low code” app and wondered if our engineering team used that. My response, I think, provides something of an answer to this paradox: it’s not writing the code that’s time consuming; it’s the requirements gathering. It’s not enough to generate code or even have the LLM build or deploy the software. It’s all the knowledge and experience around crafting an app that’s likely preventing the shovelware. Turns out code is only a part of our job.

Also, why is this the “Gorman” Paradox? He literally links to the article that I remember as first proposing this paradox (though I don’t think the original author called it a paradox). This author just summarizes that article. It should be the Judge Paradox, after the original author.

> Turns out code is only a part of our job.

Yeah. Normally, of course, I link to an XKCD, but for this observation, I like this cartoon:

https://i.programmerhumor.io/2024/12/programmerhumor-io-prog...

> Also, why is this the “Gorman” Paradox?

I just made the same point in a comment, before I read yours.

Gorman is obviously a marketing guy, but he's tech-adjacent enough he should realize this is going to go over like a lead balloon.