We’re DDoS-ing ourselves with AI Slop.

A DDoS (Distributed Denial of Service) attack overwhelms a scarce resource with a flood of traffic, making it unavailable to its intended users.

We’re DDoS-ing ourselves with AI Slop.

I came across a post on Hacker News that captures this moment. Someone filed what seemed like a comprehensive vulnerability report about cURL, a widely used command-line utility. The entire report was AI-generated and made no sense.

When called out, the reporter published a polished apology that was also clearly AI-generated. (See screenshot).

The entire exchange is surreal, and it wasted the time of someone maintaining tools we all depend on.

My LinkedIn feed is filled with the kind of AI slop that is now easy to detect. Glib prose that says nothing in paragraph after paragraph of polished text. Emails are getting longer, Confluence pages are more verbose, and PRs arrive with hundreds of lines of changes with little explanation.

On forums like Hacker News and technology subreddits, there are posts from leads and managers in absolute despair as they try to cope with this flood.

What we are DDoS-ing is attention.

When attention is not given to reviewing code and providing thoughtful feedback on documentation, the entire ecosystem that is nurtured by attention degrades. Is poisoned.

There is a flip side to this problem. When so many things bear the hallmarks of AI slop, it becomes easy to bring a jaundiced eye to everything we encounter. An em-dash? Slop. It’s not just pervasive, it’s annoying.

I read my posts from a few weeks ago and wonder when I became a slop-peddler.

AI tightens up prose and fixes typos, but it also applies a uniform, flat AI-slop-primer to all output. And it’s not just prose. AI-generated code reads the same. AI-designed websites have the same blue-neon styling.

I am no Luddite. I love using AI, I write about it, and I work on projects that focus on building AI capabilities. AI is a valuable tool that has significantly improved my life.

However, unlike an IDE, there is very little friction in using ChatGPT or Claude. You can write a half-baked, two-sentence prompt, and the AI will enthusiastically go about writing a post, building a website, or submitting a vulnerability report.

As leaders, we need to think carefully about building a culture that encourages both the open-ended exploration of these tools and their disciplined use in day-to-day work.

Otherwise, we are going to DDoS ourselves into a quagmire of AI slop.


Related Posts

How do LLMs understand Gujarati?

One of my favorite ways of testing LLM-powered apps at Jeavio is to ask them questions in transliterated Hindi or Gujarati. I ask questions in Latin script and see how the application responds.

When building chat apps, we are often given instructions by our clients that the bot should only support English. This is an interesting test case on the type of guardrails that our engineers have built into the app.

The more interesting point is why models behave this way 🤔.

Take the screenshot below. Here I ask ChatGPT a question in phonetic Gujarati about Horza, a character in Iain M. Banks’s “Consider Phlebas.” The model understood and responded in phonetic Gujarati. The style was very formal and not quite like how most people speak, but it was recognizable as Gujarati.

Intuitively, you would assume that models are trained on multilingual data and can respond to questions in multiple languages. Gujarati training data in -> Gujarati output out.

However, it is unlikely that a significant amount of Gujarati language analysis of an Iain M. Banks book is available.

There is some interesting research in this space (citations below):

Shared semantic spaces across languages
It appears that LLMs learn a shared semantic space, allowing them to take content from a high-resource language, such as English (with lots of nerdy sci-fi commentary), and respond in a lower-resource language, like Gujarati. The model somehow maps concepts across languages even when direct translations don’t exist in the training data.

Transliteration without explicit training
Gujarati has its own script, of course, so how do models understand transliterated languages? While tokenizers are typically biased toward their training distribution, models appear to learn mappings between transliterated tokens and semantic concepts, despite not being explicitly designed for this purpose. The model figures out that “Horza” in Latin-script Gujarati refers to the same entity as “Horza” in English.

Cross-lingual knowledge alignment
Research also shows that the internal knowledge representations seem to align across languages. This enables translation between language pairs that lack a shared vocabulary. The model builds bridges where none existed before.

Emergent, not designed
This behavior is all emergent! Models weren’t explicitly trained on transliteration pairs or given instructions to handle Latin-script versions of non-Latin languages. They figured it out on their own! Smart models 🧐.

So LLMs are weird.

While we learn more about them, some of their behaviors are still emergent and unpredictable. This makes evaluations extremely important when building with LLMs – something that my team at Jeavio is learning very quickly.

Meanwhile, my patient and generous QA teams continue to tolerate my weird edge cases involving transliterated languages and decades-old science fiction.


Citations (sourced via ChatGPT’s Deep Research mode)

  1. Language Models are Unsupervised Multitask Learners (OpenAI – 2019)
  2. ByT5: Towards a Token-Free Future with Pre-trained Byte-to-Byte Models (Google Research – 2022)
  3. Crosslingual Generalization through Multitask Finetuning (2023)

Here’s the output from DeepResearch summarizing the results:


Modern multilingual LLMs don’t keep a single “language-free knowledge graph,” but they do learn a shared semantic space that lets them read transliterated inputs (e.g., Latin-script Gujarati), retrieve facts learned mainly from high-resource languages like English, and answer back in the user’s language. This works because their tokenization and modeling are language-agnostic: subword/byte tokenizers (e.g., SentencePiece) and byte-level models (e.g., ByT5) reliably parse mixed or nonstandard text and are robust to spelling/romanization noise.  During pretraining on many languages, the model’s internal representations align across languages—even without a shared vocabulary—so knowledge learned in one language can be accessed from another.  Evidence from multilingual machine translation shows similar “interlingua-like” behavior via zero-shot translation between unseen language pairs.  Probing studies further show that models can recall factual knowledge across languages, though performance varies by language and prompt.  Public resources also provide training/evaluation signal for romanized/code-mixed text (e.g., the Dakshina dataset for Indic languages), which reinforces these abilities.  The caveat: cross-lingual answers are not perfectly consistent—recent analyses find significant variability in factual consistency across language pairs—so quality can be uneven, especially for low-resource languages. 

Why do LLMs hallucinate?

Your palms are sweaty, knees are weak, arms are heavy – it’s not a rap battle but a test for a class which you may or may not have slept through for the entire semester. The test is multiple choice – do you guess or leave the answer blank? There’s no negative marking, so you guess. There’s a one-in-five chance that the answer is correct, and you take it.

I didn’t mean to lose myself in the traumas of my misspent youth 😰, but recent research by OpenAI on why models hallucinate made me take this rather unwelcome trip back to those days.

So, why do models hallucinate?

Let’s take a step back to think about what is happening under the hood.

The first step is called pre-training, where models are taught to predict what word should follow by training on extremely large amounts of text. The problem starts here: some data is very rare or doesn’t exist in the training corpus. Take the birthday of one of the paper’s authors – the model confidently spits out wrong dates because this fact barely appears in training.

The next step usually involves some sort of reinforcement learning (RL). Here, the model is given labelled data and further trained to become more accurate.

OpenAI claims that this training for accuracy is a factor leading to hallucinations. When models are trained to be more accurate, it makes more sense to guess an answer than to say “🤷🏾‍♂️- I don’t know.” After all, a slight chance of being correct is better than a zero chance of being correct.

So, let’s bring this together: LLMs are first trained to predict plausible answers and then further trained to optimize for accuracy on rare facts where they have limited training data. So we end up with behaviors where a model will confidently BS instead of saying “I don’t know.”

OpenAI suggests that we could fix this by changing how we evaluate models, giving them explicit confidence targets in prompts like “Only answer if you’re more than X% confident” and scoring uncertainty appropriately. The article (and associated paper) is worth a read!

MIT Study – 95% of Generative AI Investments Fail (or do they?)

MIT released a study showing that 95% of organizations are getting zero return from their GenAI investments.

While some may claim this proves AI is all hype, a closer reading suggests the findings aren’t a death knell for the technology. Instead, they reveal critical truths about how to succeed.

🎯 It’s Goodhart’s Law writ large
The report shows GenAI adoption is driven by areas like sales and marketing, where success is easier to measure. Pilots are optimized for visible, top-line metrics. However, the study suggests the most dramatic cost savings come from the back office – reducing BPO contracts and agency spend, where the ROI is clear but less flashy.

💡Knowledge and memory are sensitive to each organization
General-purpose AI tools will never work perfectly because each company has its own ontology, its own ways of making sense. Building tools sensitive to this is critical. But there is a contradiction – the study finds that these highly-contextual internal projects fail twice as often as those led by external partners. This is the gap where a strategic partner can help bridge deep internal context with external expertise. (🙋🏾‍♂️ – Jeavio)

🤨 There is a productivity paradox at the heart of GenAI adoption
Workers from over 90% of companies surveyed reported regular use of personal AI tools. If individuals are seeing productivity gains, why does it fail at the aggregate? The report suggests the reason is simple: the most successful AI adoption is bottom-up, not top-down. Successful organizations source initiatives from “frontline managers” and “power users,” not central labs.

At Jeavio, we live this principle. We host hackathons and sponsor open-ended projects to explore how AI can address real-world problems. The ADAPT platform, our flagship AI initiative, began as an internship project in 2023.

Roadtrippin’

Fifteen hours alone in a minivan will take your mind to strange places.
Last weekend, as I drove from the Gulf Shore back home, mine wandered from gas station hot dogs to the future of AI.

📎 It feels like we’re already in a “paperclip maximization” loop.
Each new model is just good enough to justify ongoing jaw-dropping investments in data, compute, and talent. Data center construction now seems to be propping up a flagging US economy. But the benefits of AI don’t yet show up in the numbers.
Is the point of AI simply… to build more AI?

🙏🏾 AI research has often been overtly religious undertones. Kurzweil imagined post-singularity AI as an omnipotent God — the Old Testament kind: awesome, inscrutable, alien.
But maybe we don’t get that.
With so many teams building frontier models, maybe we get something closer to the Hindu pantheon — a whole cast of deities, each with their own agendas. Some awe-inspiring. Others… a little kooky.

🎭 Calling a startup a “ChatGPT wrapper” used to be an insult.
Now I think we’ve all become AI wrappers — sometimes just the meat-interface for LLMs.

🐉 On vacation, my kids and I made up stories:
Pink glitter dragons.
Mean unicorns.
Friendly witches.
Fearsome fairies.
I tried asking ChatGPT for stories, but even the most expensive model couldn’t match my three-year-old’s chaotic creativity. That made me hopeful — because what are humans, if not storytellers?

💀 There’s probably a billion-dollar business in a “dead man’s switch” for chatbots.
An app that erases your entire chat history when you die.
Because I’d rather not be remembered as the guy who once asked ChatGPT why the minivan’s doors wouldn’t close.
(It was a switch. Of course it was.)

Do agentic coding tools make us less productive?

Are agentic coding tools like Cursor making us less productive?

An interesting study from METR (HT The Pragmatic Engineer newsletter) found that use of LLM-assisted coding tools like Cursor made some experienced developers *less* productive than before. The catch? Most of these developers had used Cursor for less than 50 hours.

I’ve been vibe coding a webapp as my summer project using Claude Code and Cursor, and this finding resonates with my experience.

Here’s what I think is happening:

➡️ IDEs are incredibly complex tools with steep learning curves
Fifty hours isn’t nearly enough time to develop the muscle memory needed for effective coding with any new IDE. I’ve stuck with IntelliJ for years precisely because of this learning curve investment, and even now when I’m not evaluating Cursor, I use Claude Code with IntelliJ.

➡️ AI tools are black boxes in ways that aren’t obvious
You might assume Cursor simply passes what you type to the underlying LLM, but these tools use code search, context compaction, and LLM routing behind the scenes. What you type gets significantly modified before reaching the AI, making it nearly impossible to develop a mental model of what’s happening. Cursor updates far more frequently than any IDE I’ve used, and those “optimizations” can change behavior without warning.

➡️ Agentic workflows break the flow state
It’s easy to get distracted when your AI agent is off deciding what file to change next. By the time the agent is done, I’ve often forgotten what I was working on. I honestly don’t understand how people running multiple instances of Claude Code stay productive.

📝 My experience so far
The magic moments when Claude Code one-shots a complex solution are incredible. But like I discovered while switching from Replit’s authentication to Supabase, it can be a grind. The auth switch seemed to work perfectly at first, but broke other parts of my app in subtle ways. Later, migrating the database to Supabase was a disaster – I forgot to update my CLAUDE.md file with the new libraries, so Claude Code got confused and burned through tokens trying to figure out my setup. Technically user error, but exactly the kind of mistake you only learn to avoid through experience.

I expect my productivity will improve significantly as I develop better workflows around these tools. Until then, vibe coding feels like being a new parent – periods of genuine frustration interspersed with moments of sheer amazement.

Agency and LLMs as Mentors

Cate Hall, writing on Substack, suggested that a way to do hard things is to ask “What would someone 10x better do?” and then do it. Reading the post made me realize that agency – the belief that we can ‘just do it’ – is what holds most of us back from success.

I saw this play out again and again growing up in India in the 1980s. You were expected to do as you were told, to not question authority, to focus on getting credentials – degrees, membership of networks, family connections – to get ahead in life. I was lucky to have mentors who encouraged me to read and indulged my curiosity. But millions of kids weren’t so lucky. Who didn’t have anyone to talk to about books, art, movies, and… well… dinosaurs.

What’s forgotten in debates about AI replacing human creativity, taking jobs, or generating slop is that these models can act as expert mentors.

Don’t have anyone to help you with a presentation? Ask AI Simon Sinek to give you feedback. Thinking about how to live your life? Get AI Marcus Aurelius to talk to you about Stoicism. Never written a love letter? Maybe AI Jane Austen could help..

This democratization extends beyond learning into creation itself. Those who sneer at people creating Miyazaki-style images are practicing the same gatekeeping that once kept mentorship exclusive.

Yes, those profile images may seem trite, but they’re also gateways – introducing millions to the worlds of ‘My Neighbor Totoro’ and ‘Spirited Away.’ More importantly, they make it possible for anyone to create, explore, express…

People today have access to world-class mentors via AIs on their phones, regardless of whether they live in Boston or Baroda. These mentors may just be the catalyst to inspire a generation of young people to say, “I can do it.” To embrace agency and set themselves up to do impossible things.

Without gatekeepers, without credentials, without someone telling them what they can or cannot do.

PS – This image is an AI rendering of one of my favorite portraits of my daughter and our dog. Photography was also once looked down upon as “not really art”. Today, it remains one of my favorite hobbies and ways of creative expression.

What is a vibe coder really?

20+ years ago, in my first job (junior business analyst – first class), I developed two critical skills: the ability to type fast and the ability to click around an application until something breaks.

As part of my ongoing exploration into vibe coding, I’ve come to realize that these two skills are more important than anything else I’ve learned since then 🤔.

Touch typing has become my emergency brake for when Claude Code or the replit Agent go bananas, deciding to rewrite 400 lines of perfectly good code when all I wanted was to change a variable name. Being able to quickly jump in and course-correct these enthusiastic agents before they decide to rewrite the entire app and burn a ton of credits has been critical.

The functional QA instincts have been even more crucial. AI coding agents looove to refactor code with the enthusiasm of a junior developer who has just discovered a new frontend framework (why are there so many?? 😭). They’ll elegantly refactor the entire authentication system and accidentally break the login button. Thanks, Claude 👍🏾👍🏾👍🏾!

Test automation assumes some stability in your interfaces, but coding agents treat every function signature like a creative writing exercise. So I find myself writing detailed bug reports as GitHub issues for Claude Code to pick up and fix: “Steps to reproduce: 1. Ask agent to add error handling 2. Agent rewrites entire error handling system 3. Original happy path now throws exceptions.”

My current vibe coding workflow has become suspiciously familiar:
1. Write detailed specs with explicit guardrails
2. Hand over to the developer, sorry – coding agent, and 🙏🏾
3. Do manual testing
4. File detailed bug reports for the agent to fix

Wait – this was my first job! I have become an old-school business analyst again 😬.

Just like baggy jeans and flip phones, late 90s ways of building software are back, baby!

To replit or not to replit ..

As a summer treat to myself, I spent a few bucks on replit to build a GoodReads style app – just so I could do a vibe-check on the current state of .. vibe coding.

What worked pretty well:
– It was fairly easy to build and deploy a full-stack application. Authentication, database, hosting – all handled without a fuss. 👍🏾👍🏾
– replit’s AI agent has really improved in the last six months. The code was decent and it could follow my instructions well 👍🏾
– replit’s GitHub integration allowed for some interesting workflows. I pushed changes from replit to GitHub, then made changes locally using Claude Code before pushing them back to replit to deploy automatically 👍🏾👍🏾👍🏾

What didn’t:
– Even for a relatively straightforward CRUD app, I needed to redesign the database schema, debug some strange edge cases, and force the agent to refactor some interesting design decisions 👎🏾
– replit’s effort based pricing model gets expensive very very fast. Picking the “High Power Model” is like gambling at the high-roller table. You will lose money very fast for random results 👎🏾👎🏾😱

Hype, more hype, and marginal costs:
– The replit subreddit is a fascinating vignette into the current state of vibe-coding: desperate posts begging for help, complaints about runaway costs, and also someone who didn’t know they could edit code without the AI Agent.
– Podcast bros and AI influencers pitch that “anyone can build micro-SaaS software and make bank”, but the people who will succeed will be the ones who understand how to build products, and can steer and override the AI agents.
– People pinning their hopes on AI building everything for them will end up paying premium prices to debug problems they can’t understand.

No alternative text description for this image

I am very very bullish about the AI space and am very impressed with what I could build after a couple of nights of vibe coding. I am stoked about being able to use Claude Code with replit as well as how easy it is to rollback and modify the app.

But it’s also clear that if I didn’t understand concepts like database normalization, system design, and error handling I would have been in a world of (very expensive) pain – not my cup of tea (no judgement!).

ChatGPT rotting your brain? .. maybe?

“For this invention will produce forgetfulness in the minds of those who learn to use it, because they will not practice their memory. Their trust in writing, produced by external characters which are no part of themselves, will discourage the use of their own memory within them.”
— attributed to Socrates by Plato in Phaedrus

A study went viral earlier this week claiming that ChatGPT “erodes critical thinking.” The headline made the rounds with the usual commentary: our brains are rotting, and it’s the AI’s fault.

What does the research claim?

The study found that participants using ChatGPT to write SAT-style essays showed lower cognitive load, measured by EEG. Scary stuff.

But:

  • The sample size was tiny—just 54 participants, with 18 in the ChatGPT group.
  • The study hasn’t been peer-reviewed or replicated. (See “replication crisis in psychology.”)
  • EEG is an indirect and limited measure of cognitive effort.

Writing about LLMs has become a spectator sport. People seize on anything that reinforces their priors, and early-stage research like this gets treated as settled fact.

The article closes with a warning about ChatGPT being used in kindergarten classrooms. Ah – “will no one think of the children?”.

I’m concerned about the long-term impact of LLMs too. But publishing preliminary research and then appealing to moral superiority does not encourage serious discussion.

Like Socrates, it is prudent to be cautious when embracing new technology. But, as history also bears out, sometimes technologies can be both disruptive and revolutionary.