Almost all opinion pieces are like that. They lack information density, but some readers (like me) like them that way. Otherwise, I'd only read one-line summaries.
replyI guess some people don't like articles that don't deliver a skill.md to solve a problem.
replyFor me the article is about programmer culture and work ethics, it's hard to discuss with hard facts. Yet sharing this personal experience is valuable.
I mean, go look at the author's linkedin and github. They're a "dev" with 20 years of 1 year of experience. Not a software "engineer"
replyThere's a big difference between the two and LLMs are increasing the chasm. The Software devs are crying out because the LLMs can already do their full job. Software engineers are happy because the LLMs are removing a large chunk of the job that's low value.
Software dev using an LLM is gonna produce "slop"
Software engineer using an LLM is going to have an increase in productivity depending on how they're using the LLM tools.
There is no universally accepted distinction between developer and engineer.
replyEven if so, dev or engineer, both can be low or high skill. Their job title doesn't tell how sloppy or good their LLM usage will be.
This isn't about distinction between literal titles. But continue missing the point.
replyYou make up an false dichotomy. The differentiation between the title and the supposed skill level based on title, is neither true nor helpful to make your point.
replyThere's no false dichotomy. You're just choosing to miss the point to argue semantics.
replyWell you could make your point clear, instead you keep acting like I am hostile.
replyYeah it is. The meat of your post is textbook gatekeeping. "This is a dev, not an engineer."
reply