The 8 Levels of AI Adoption for Engineers (And the Resources for Each)

The world of software engineering is changing faster than ever. Every week, there is a new AI tool, a new model, or a new way to write code. It is easy to feel left behind. You might wonder if you are using AI the right way. You might wonder if you are falling behind your peers.

Recently, Gergely Orosz hosted Steve Yegge on The Pragmatic Engineer podcast. The episode was a deep dive into how AI is changing our jobs. You can listen to the full episode here: From IDEs to AI Agents with Steve Yegge.

In this episode, Steve shared a brilliant framework. He argued that software engineers exist on a spectrum of AI adoption. There are 8 distinct levels. On one end, you have engineers who avoid AI completely. On the other end, you have engineers running massive swarms of AI agents in parallel.

Steve also talked about the "prototype-as-product" model and the "Gas Town" agent orchestrator. He explained why technical knowledge keeps changing so fast. Most importantly, he stressed that AI is here to amplify engineers, not replace them. But this rapid pace also creates a new kind of technical debt. If you do not keep up, your skills might become outdated.

The big takeaway? No matter what level you are at on the AI adoption ladder, there is a specific set of sources you need to follow to level up. You need to read the right newsletters, watch the right YouTube channels, and follow the right people.

But there is a catch. Following all these sources can lead to massive information overload. Your inbox gets flooded. Your bookmarks pile up. You spend more time organizing links than actually learning.

In this post, we will break down Steve Yegge's 8 levels of AI adoption. For each level, we will look at how an engineer thinks and works. We will also give you specific resources to help you move to the next level. Finally, we will show you how to use a tool called Nestornotes to follow all these sources without drowning in the noise.

---

Level 1: The Avoider

At Level 1, the engineer ignores AI. They might think it is just a passing trend. They might think it is a hype bubble that will pop soon. Or, they might have tried an early version of ChatGPT, found it made a mistake, and decided it was useless for real work.

The Avoider still writes every line of code by hand. They search Stack Overflow for answers. They read official documentation from start to finish. They are proud of their craft, and they feel that using AI is somehow "cheating."

The problem is that the industry is moving on. The Avoider is competing with engineers who are working twice as fast.

How to level up: If you are at this level, you do not need to jump into building complex AI apps. You just need to start reading about how other companies are using AI. You need to see the real-world impact.

Resources to follow:

• The Pragmatic Engineer Newsletter: Gergely Orosz writes about how big tech companies operate. He covers AI trends in a very grounded, practical way.
• Hacker News: This is the front page of the tech world. Just reading the headlines will show you how much the industry is focusing on AI.
• TechCrunch: Keep an eye on the startups getting funded. You will notice that almost all of them have an AI component.

Level 2: The Dabbler

The Dabbler has accepted that AI is real. They have an account on ChatGPT or Claude. They use it, but only for simple things.

They might ask the AI to write a regular expression. They might ask it for a recipe for dinner. They might use it to write a polite email to their boss. But they do not trust it with their core engineering work. They treat the AI like a smart search engine, not a coding partner.

The Dabbler is curious, but they have not integrated AI into their daily workflow. They still switch contexts constantly. They leave their code editor, open a browser, ask a question, and then go back to the editor.

How to level up: The Dabbler needs to learn what these models are truly capable of. They need to see examples of complex prompts and clever use cases.

Resources to follow:

• TLDR AI Newsletter: A daily summary of the most important AI news. It takes five minutes to read and keeps you in the loop.
• The Rundown AI: Another excellent daily newsletter that highlights new tools and creative ways to use AI.
• Ethan Mollick's Blog (One Useful Thing): Ethan writes brilliantly about how to use AI for everyday knowledge work. He shows how to push the models to do real thinking.

Level 3: The Copilot Coder

This is where AI starts to change how an engineer works. The Copilot Coder has installed an AI assistant directly into their IDE. They use GitHub Copilot, Cursor, or Codeium.

At Level 3, the engineer is no longer typing every character. They write a comment, and the AI writes the function. They start typing a variable name, and the AI finishes the line. The AI acts as a super-powered autocomplete.

This saves a massive amount of time on boilerplate code. The engineer can focus more on the logic and less on the syntax. However, the Copilot Coder still treats the AI as a junior assistant. They review every line carefully. They do not ask the AI to design the system; they only ask it to fill in the blanks.

How to level up: To move past autocomplete, you need to learn how to use AI for larger tasks, like refactoring whole files or writing tests.

Resources to follow:

• Fireship (YouTube): This channel provides fast, high-energy updates on new web technologies and AI tools. It is perfect for seeing new coding workflows in action.
• GitHub Blog: Follow the official updates from GitHub. They frequently post tutorials on how to get the most out of Copilot.
• Cursor Community Forum: If you use the Cursor IDE, their forum is a goldmine. Users share amazing tips on how to use the built-in AI to edit multiple files at once.

Level 4: The AI-First Developer

The AI-First Developer has fundamentally changed their workflow. When they face a bug, they do not go to Google. They paste the error trace into Claude or GPT-4. When they need to learn a new library, they ask the AI to explain it to them with examples.

At this level, the engineer is actively having conversations with the AI about architecture and design. They use the AI as a sounding board. They understand the strengths and weaknesses of different models. They know that Claude 3.5 Sonnet is great for coding, while GPT-4o might be better for general reasoning.

They are also getting good at "Prompt Engineering." They know how to give the AI context. They know how to ask the AI to think step-by-step.

How to level up: You are already a power user. Now, you need to start looking under the hood. You need to understand how these models are built and how to interact with them via code, not just chat interfaces.

Resources to follow:

• Anthropic and OpenAI Official Blogs: Read the release notes when new models come out. Understand the benchmarks and the new capabilities.
• Prompt Engineering Guide (promptingguide.ai): This is a comprehensive open-source guide on how to write advanced prompts. It covers techniques like Few-Shot Prompting and Chain of Thought.
• Simon Willison's Weblog: Simon is a fantastic developer who writes extensively about how he uses AI in his daily work. He shares his exact prompts and workflows.

Level 5: The Tool Builder

At Level 5, the engineer crosses a major threshold. They stop just using AI tools and start building them.

The Tool Builder signs up for API keys from OpenAI, Anthropic, or Google. They write scripts that call these APIs. They might build a script that automatically summarizes their daily standup notes. They might build a Slack bot for their team that answers questions about the company handbook.

They learn about RAG (Retrieval-Augmented Generation). They learn how to take a PDF, chop it into pieces, store it in a vector database, and let an LLM answer questions about it. They are turning AI into custom software.

How to level up: Building simple scripts is great. But to go further, you need to learn how to give the AI tools. You need to let the AI take actions on its own.

Resources to follow:

• Latent Space Podcast & Newsletter: Hosted by swyx and Alessio, this is the best resource for "AI Engineers." They interview the people building the cutting edge of AI.
• LangChain and LlamaIndex Documentation: These are the two most popular frameworks for building AI applications. Reading their docs and tutorials is essential.
• DeepLearning.ai Short Courses: Andrew Ng's platform offers free, short courses on things like building RAG systems and using LLM APIs.

Level 6: The Agent Explorer

The Agent Explorer is fascinated by autonomy. They do not just want to ask an AI a question; they want to give the AI a goal and let it figure out the steps.

They experiment with tools like AutoGPT, BabyAGI, or Devin. They watch as the AI writes a plan, searches the web, writes some code, runs the code, sees an error, and fixes its own mistake.

At this level, the engineer realizes that AI can be an independent worker. However, they also see the limitations. They know that agents often get stuck in loops. They know that agents can hallucinate and go off track. The Agent Explorer spends a lot of time tweaking prompts and guardrails to keep the agent focused.

How to level up: A single agent is limited. To solve bigger problems, you need multiple agents working together.

Resources to follow:

• GitHub Trending (Python/TypeScript): Keep an eye on the trending repositories. Whenever a new open-source agent framework drops, it will show up here first.
• Arxiv Digests / AK (@_akhaliq) on Twitter: Follow the latest AI research papers. You do not need to read the math, but you should read the abstracts to see where agent research is heading.
• Harrison Chase (LangChain CEO) on Twitter/LinkedIn: He constantly shares insights on how developers are building agents in the real world.

Level 7: The Agent Orchestrator

This is where Steve Yegge's concepts really shine. The Agent Orchestrator builds systems where multiple AI agents talk to each other. Steve calls this the "Gas Town" model.

Imagine a software factory. You have a "Product Manager Agent" that writes the specs. You have a "Developer Agent" that writes the code. You have a "QA Agent" that writes the tests. The Orchestrator builds the system that manages these agents. They set up the communication channels. They decide how the agents resolve disagreements.

The Orchestrator treats AI models like microservices. They know that a complex task is best solved by breaking it down and assigning different parts to different, specialized agents.

How to level up: You are building complex systems. The next step is scale and speed. How do you run these systems massively in parallel?

Resources to follow:

• r/LocalLLaMA (Reddit): This community is obsessed with running AI models locally. It is a great place to learn about efficiency, fine-tuning, and running multiple models cheaply.
• Microsoft AutoGen Documentation: AutoGen is a framework specifically designed for building multi-agent conversations. Studying their examples will teach you a lot about orchestration.
• Discord Communities (e.g., LangChain, LlamaIndex): The real advanced discussions happen in these Discord servers. Join the channels focused on agents and orchestration.

Level 8: The Parallel Commander

This is the final level in Steve Yegge's framework. The Parallel Commander does not just run a few agents; they run hundreds or thousands of them at the same time.

They treat AI like a massive parallel computing cluster. If they need to refactor a codebase with 10,000 files, they do not do it one by one. They spin up 10,000 agents, give each one a file, and execute the task in seconds.

They understand that LLM calls are cheap and fast. They use this to their advantage. They build systems that explore multiple solutions to a problem simultaneously, evaluate them all, and pick the best one. The Parallel Commander is not just writing code; they are directing an army of digital workers.

Resources to follow:

• Steve Yegge's Blog / Podcast Appearances: Keep following Steve. He is actively building at this level and sharing his learnings.
• Cutting-Edge AI Engineering Conferences (e.g., AI Engineer World's Fair): Watch the keynotes and technical talks from these events. This is where the future is being built.
• Research papers on "Tree of Thoughts" and "Agent Swarms": Dive into the academic research on how to make large groups of LLMs work together efficiently.

---

The Problem: Drowning in the Noise

Look back at the resources listed above. Newsletters, YouTube channels, subreddits, Discord servers, GitHub repos, research papers, and podcasts.

If you want to move up the levels of AI adoption, you have to consume a lot of information. The knowledge in this field keeps changing. What was true six months ago is outdated today.

But here is the painful reality for most software engineers: We are drowning in information overload.

You subscribe to five newsletters, but you never have time to read them. They just pile up in your inbox, making you feel guilty. You save YouTube videos to your "Watch Later" playlist, which now has 400 videos in it. You join Discord servers, but the chat moves so fast that you cannot keep up.

You suffer from FOMO (Fear Of Missing Out). You worry that if you miss one important article, you will fall behind. But trying to read everything leaves you exhausted. You spend your weekends trying to catch up on tech news instead of relaxing or actually writing code.

You need a way to turn this chaotic flood of information into organized, useful insights. You need a system that does the heavy lifting for you.

The Solution: Nestornotes

This is exactly why we built Nestornotes.

Nestornotes is an AI-powered "second brain" designed specifically for software engineers and knowledge workers who are tired of information overload. It is a single place to gather, digest, and query everything you need to learn.

Here is how Nestornotes helps you climb the AI adoption ladder without losing your mind:

1. A Centralized Hub for All Your Sources

Instead of checking your email, Twitter, YouTube, and RSS reader separately, you connect them all to Nestornotes. You create "Collections" based on your interests. For example, you can create a collection called "AI Engineering."

You can route newsletters directly into this collection using a dedicated Nestornotes email address. You can add RSS feeds from the OpenAI blog. You can drop in links to Fireship YouTube videos. You can even upload PDF research papers. Everything lives in one organized place.

2. Automatic AI Summarization

You do not have time to watch a 45-minute podcast or read a 3,000-word article every day. Nestornotes fixes this. Whenever new content arrives in your collection, Nestornotes automatically digests it. It reads the articles, transcribes the videos, and generates concise, bullet-point summaries. You can understand the gist of a complex topic in seconds.

3. Nestor AI: Your Second Memory

This is where the magic happens. Nestornotes comes with an AI assistant called Nestor AI. You can literally chat with your own collections.

Imagine you vaguely remember reading about the "Gas Town" model a few weeks ago. Instead of searching through your inbox, you just ask Nestor AI: "What was that Gas Town agent model Steve Yegge talked about, and what tools were mentioned?" Nestor AI will instantly search your saved podcasts, newsletters, and articles, and give you a precise answer with citations.

You can also use Nestor AI to generate new content. You can say, "Based on the AI newsletters I received this week, write a short summary of the top 3 new coding tools."

4. Calm Digests (No More FOMO)

Constant notifications ruin your focus. Nestornotes protects your attention. Instead of pinging you every time a new article drops, it sends you a scheduled daily or weekly email digest.

This digest summarizes the key updates from all your collections. It gives you exactly what you need to know, exactly when you want it. You can even add widgets to your digest, like the weather or stock prices, for a personalized morning briefing.

Clear Your Inbox, Organize Your Mind

The pace of AI development is not going to slow down. If anything, it is going to speed up. The engineers who succeed will be the ones who figure out how to manage this flow of information.

You can choose to stay at Level 1 and ignore the noise. Or, you can build a system to handle it.

Stop letting unread newsletters pile up in your inbox. Stop losing great YouTube tutorials in your watch history. Start treating your knowledge like a valuable asset.

Try Nestornotes today. Turn your information overload into organized insights, clear your inbox, and start climbing the levels of AI adoption with confidence.