๐Ÿชฃ 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