๐ชฃ AI slop didnโt start with AI. | Antony Kelly
Originally published on LinkedIn
๐ชฃ ๐๐ ๐๐น๐ผ๐ฝ ๐ฑ๐ถ๐ฑ๐ปโ๐ ๐๐๐ฎ๐ฟ๐ ๐๐ถ๐๐ต ๐๐. I love the term โAI slop.โ Now widely used derogatorily by engineers defending an invented battle against AI โ one that should accelerate them if they were real engineers not coders, not threaten them.
But letโs be honest.
๐ ๐๐ ๐๐น๐ผ๐ฝ ๐ฑ๐ถ๐ฑ๐ปโ๐ ๐๐๐ฎ๐ฟ๐ ๐๐ถ๐๐ต ๐๐.
๐ It started with engineers โ long before AI.
๐งฑ ๐ ๐ฎ๐ป๐๐ฎ๐น ๐๐น๐ผ๐ฝ has been the norm for years. Otherwise we wouldnโt need quality gates, safety nets, code reviews, static analysis, PRs and checklists, and entire process layers to stop slop escaping.
As an industry, weโve accepted that slop goes in from engineers, and built slow, complex processes to contain it. It's now just easier and more convient to call out AI than the engineer next to you.
Now AI enters.
An engineer throws in a vague prompt โ one that would never be acceptable if handed to another engineer setting an impossible bar.
๐ค AI fills the gaps.
๐ Generates something.
๐๏ธ Itโs called โAI slopโ.
And then the engineer responsible says > โSee? Just AI slop it canโt codeโ
But letโs be clear:
โ ๐ง๐ต๐ฒ ๐๐น๐ผ๐ฝ ๐ฑ๐ถ๐ฑ๐ปโ๐ ๐ฐ๐ผ๐บ๐ฒ ๐ณ๐ฟ๐ผ๐บ ๐๐ต๐ฒ ๐๐.
โ ๐๐ ๐ฐ๐ฎ๐บ๐ฒ ๐ณ๐ฟ๐ผ๐บ ๐๐ต๐ฒ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ.
AI is just a mirror of the skill and effort of the engineer at the helm who's responsible for the quality of the output.
Lets be frank, many engineers donโt actually engineer, they just code.
They make something that works. The next engineer calls the code slop. More engineers are paid to fix it, often with โletโs rewrite the code.โ and more slop in the eyes of the next engineer. Code is subjective, the goals and engineering requirments aren't which should be the focus.
So the real question isnโt โCan AI code?โ it's ๐ฅ ๐๐ฟ๐ฒ ๐๐ฒ ๐ฐ๐ผ๐ฑ๐ถ๐ป๐ด โ ๐ผ๐ฟ ๐ฎ๐ฟ๐ฒ ๐๐ฒ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ถ๐ป๐ด?
Some uncomfortable questions:
1๏ธโฃ ๐จ๐ป๐ถ๐๐ฒ๐ฟ๐๐ถ๐๐ How much engineering is taught โ and how much is just coding?
2๏ธโฃ ๐๐๐ป๐ถ๐ผ๐ฟ & ๐บ๐ถ๐ฑ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ How much are they taught to think like engineers, mentored effectivity versus being told to โjust ship codeโ? Learning by bad code examples rather than principles.
3๏ธโฃ ๐ฆ๐ฒ๐ป๐ถ๐ผ๐ฟ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐ How many are engineers โ not just coders being doing it too long so get a title?
If that number were small why would constant rewrite desires dominate our industry. The reason is just subjective views of code.
Those systems werenโt built by AI they were built by senior engineers manually and later called slop.
๐จโ๐ป ๐ ๐ฐ๐ผ๐ฑ๐ฒ๐ฟ ๐๐ถ๐๐ต ๐๐ says: > โThatโs not the code I wanted.โ Will rework for no real business value or objective need.
๐ง ๐๐ป ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ ๐๐ถ๐๐ต ๐๐ says: > โCode is good enough and a means to an end.โ Pragmatically delivering value.
Engineers build systems. Code is just a building block.
๐ ๐๐ ๐ฑ๐ผ๐ฒ๐๐ปโ๐ ๐ฟ๐ฒ๐ฝ๐น๐ฎ๐ฐ๐ฒ ๐ฒ๐ป๐ด๐ถ๐ป๐ฒ๐ฒ๐ฟ๐. It exposes who never was one.
๐ Fell free to argue in the comments, especially if you are one of the "AI slop" commentors
๐ | 146 comments on LinkedIn