Full transcript
0:00A developer emailed me lately and his
0:02message has been stuck in my head ever
0:04since.
0:05His company is replacing senior
0:07developers, not with other seniors, but
0:10with mid-level devs, and in some cases
0:13with juniors.
0:15Why? Not because they are cheaper,
0:18though they are, but because they are
0:20faster. They know how to work with AI,
0:23and he does not.
0:25Yet.
0:26So, he's now job hunting, and here is
0:29the part that got me. He said he
0:31understood the decision. He could see
0:34exactly why this company did it. He
0:37watched his colleagues run circles
0:39around him with AI, and he got it.
0:42So, today I want to answer the scary
0:44question head-on. Are juniors actually
0:48more valuable
0:49than seniors now? And whatever stage of
0:51your career you are at, I promise you
0:54the answer is better than you think.
0:56But, you do have to do something about
0:59it. Now, if we haven't met, hi, I'm
1:01Patrick. I've been coding for almost 30
1:03years now, from QuickBasic and Turbo
1:05Pascal as a kid, to about 20 years in
1:08.NET. I have built SaaS products, line
1:10of business applications, even video
1:12games. And these days, I teach thousands
1:15of developers. So, I am not reacting to
1:18a headline here. I have lived through a
1:20few of these moments where the ground
1:23moves under our feet, and I want to walk
1:25you through this
1:27honestly. What it actually is and what
1:30it is not. So, let me be straight with
1:32you, because most people are either
1:34ignoring this or panic posting about it,
1:37and neither helps you. This is happening
1:40right now. Companies are making these
1:42calls today, not in 5 years. So, I'm not
1:45going to tell you to relax and that AI
1:48is just hype. That would be a lie, and
1:51it would not help you. But,
1:53I am also not going to doom post and
1:55tell you anyone is finished because that
1:58is also a lie and and even more harmful
2:01one. The truth, as always, is in the
2:03middle and once you see it clearly, you
2:05will know exactly what to do. So, let us
2:08get into this. First, the most important
2:11reframe in this whole video, it is not
2:13juniors beating seniors. That is the
2:16wrong way to see it. What is actually
2:18happening is that AI fluent developers
2:21are beating AI illiterate developers.
2:24That is the real dividing line. It just
2:26so happens that a lot of the AI fluent
2:28ones are earlier in their careers right
2:31now because they had less to unlearn and
2:34they jumped in early. But, the line is
2:36not age. The line is not years of
2:39experience. The line is whether you know
2:42how to work with these tools or not.
2:45And that should make everyone watching
2:48feel a lot better, actually, because if
2:50the advantage came from being a certain
2:53age, half of you would be stuck. There's
2:56nothing you could do about that. But, it
2:59does not come from age. It comes from a
3:01skill. And skills can be learned by
3:04anyone, including you, of course.
3:06So, stop asking how do I compete with
3:09younger developers or how do I catch up
3:11to the seniors? This is the wrong
3:13question. The right question is, how do
3:16I become AI fluent and how do I do it
3:19fast? That question has an answer and it
3:22is the same answer at every level. And a
3:25quick note before I go on because that
3:28is literally what I built my four-week
3:31Blazer AI accelerator for, taking .NET
3:33developers and making them genuinely
3:36strong with these workflows fast. A few
3:39spots are still available, so check out
3:41the link in the video description below.
3:43And now, here's the part I really want
3:45you to hear because this is the one that
3:48should change how you feel.
3:51AI is fast, but AI is not wise. It will
3:55write 100 lines of code that look
3:57absolutely perfect and quietly get the
3:59authentication logic wrong. It will pick
4:01up a pattern that works today and
4:03becomes a nightmare in 6 months. It will
4:06confidently, cheerfully do the wrong
4:09thing.
4:10So, let me ask you, who catches that?
4:13Who looks at the beautiful, fast, wrong
4:16output and goes, "Nope, that is wrong."
4:19developer with judgment. The person who
4:22has seen things break, who feels when
4:25something is off. Really, have you felt
4:27It is a feeling. The developer who knows
4:30what good actually looks like because
4:32they have built it and maintained it and
4:35been burnt by the bad version. So, that
4:38judgment is the single most valuable
4:40thing in an AI-heavy workflow, and
4:43experience is how you build it. So, the
4:45real winner here is not the fastest
4:47prompter. It is the developer who pairs
4:50judgment with fluency. The AI brings the
4:53speed, and you bring the thing the AI
4:56does not have, the ability to know
4:58whether all the fast output is actually
5:01correct. And if you are a senior, that
5:03is your advantage, and it is a big one.
5:06You already have the judgment. You just
5:09need the fluency on top. And if you are
5:12earlier in your career,
5:14here's your map. Build real fundamentals
5:17so you become the person who can tell
5:20good from bad and pick up these AI
5:23workflows right alongside them. The
5:25developers who pair those two things are
5:28the ones nobody can replace at every
5:30level. The ones in trouble are the ones
5:33who skipped one or the other. So, let us
5:36demystify what fluency actually is. When
5:38that developer watched his colleagues,
5:41what did he actually see? Because once
5:43we name it, it stops being a scary magic
5:47and starts being a list of things you
5:49can learn. Number one, they run several
5:51AI sessions in parallel. Not one chat
5:54waiting for it to finish, multiple tasks
5:56moving at the same time, each in its own
5:58session while they steer all of them.
6:01Number two is agentic loops. They give
6:03an agent a clear bounded task and let it
6:06work through the steps on its own
6:09instead of babysitting every single
6:11line.
6:12Number three would be agents in the
6:14pipeline. Review agents that check every
6:17pull request automatically. Planning
6:20agents that take a requirement and turn
6:22it into a whole task list without a
6:25human writing it out.
6:27And number four would be they connect AI
6:29to their real tools through things like
6:32MCP servers so the AI can actually reach
6:35the database, the services, the systems
6:37and do real work, not just talk about
6:40the code in a box. And here's the thing,
6:42none of that is genius. It is a set of
6:45workflows any developer can learn all of
6:48it in a few weeks. And the more
6:50experience you bring to directing it and
6:53catching its mistakes, the more powerful
6:55it gets in your hands. Now my next point
6:58is the idea I come back to again and
7:00again on this channel and it fits the
7:04whole thing perfectly. There are two
7:05ways to work with AI, as a passenger or
7:08as the pilot. A passenger types a prompt
7:12and just accepts whatever comes back
7:15because they cannot yet tell good from
7:18bad. When it works, fantastic. When it
7:20quietly breaks something, they do not
7:23even notice until much later. And a
7:26pilot sets up the flight. They decide
7:29the structure, they decide the
7:31boundaries, what the AI is and is not
7:34allowed to touch and then they let it
7:36run and they catch it the second it
7:39drifts because they understand
7:42what it is doing.
7:44And here's the key thing. This is not
7:46about age. Anyone can be a passenger.
7:49Anyone can be a pilot. I have seen
7:52seniors who refuse to touch AI. All that
7:55judgment just sitting there grounded and
7:57unused. And I have seen juniors learning
7:59to fly faster than people twice their
8:01experience because they are pairing real
8:04fundamentals with the tools. The trap is
8:07not being young or being old. The trap
8:10is staying a passenger. So the developer
8:12who actually wins,
8:14the one nobody replaces, is the pilot
8:17who flies. Judgment plus fluency. That
8:20is who you want to be at every stage of
8:24your career. So let me bring this home
8:26with something you can actually do this
8:29week. Do not try to learn everything at
8:32once. Pick one task you understand
8:35really well and instead of doing it by
8:37hand, try to direct an AI agent through
8:40it. Write the task out clearly. Set the
8:42boundaries. Let it run and watch where
8:44it breaks. That is where the learning
8:47is. Do that a few times and the fear
8:51starts to fade because you finally see
8:53it for what it is. Not a colleague who
8:56is better than you, just a set of
8:58workflows you can learn. And the better
9:00your fundamentals, well, the better you
9:02will be at steering them. Whatever stage
9:04you are at, if this whole topic makes
9:07you a little anxious, good. Use it. Just
9:09do not freeze and do not coast and tell
9:12yourself it is too late because it is
9:14not.
9:15If you have experience, you are closer
9:17than you think. You already have the
9:20hard part. If you are earlier on,
9:23you have less to unlearn. Both are
9:25advantages. Use the one you have. And if
9:28you want the fast structured version of
9:31exactly that, that is the whole reason I
9:34built the Blazor AI Accelerator. Four
9:36weeks, a small group of .NET developers
9:40working through these real workflows
9:42with me live, the parallel sessions, the
9:45agents, MCP, all of it. And it includes
9:48a full year of the .NET Web Academy all
9:51access pass, so you keep going long
9:53after the 4 weeks are done. A few
9:55limited spots are still available. Link
9:58is always in the video description
10:00below. And if you want a place to
10:01actually build this fluency over time,
10:04that is what the .NET Web Academy all
10:06access pass is for. The full course
10:08library, twice monthly live sessions
10:10where we work through exactly this kind
10:12of thing together,
10:14all the source code, and a community of
10:16developers doing the same.
10:19It is the steady way to keep getting
10:21stronger month after month, and the
10:24link, as always, is in the video
10:25description below. The developers who
10:28adapt are not going to lose to anyone.
10:31They are going to be the people everyone
10:34else learns from. So, go be that. And if
10:37you already want to take a glimpse at
10:39what MCP can actually do for you, one of
10:41those workflows I mentioned earlier, I
10:44suggest you check out this video here on
10:46the screen. This is where I show you
10:48exactly what it is and how to use it.
10:52Click there. I see you in this one.
10:55Take care.
10:56It is freaking hot in here.