Welcome to the Architecture Corner.
Today we're diving into a really hot topic in tech right now, AIS
impact on software development. You've probably heard the buzz.
Maybe coding is dead or even calls to, you know, dismiss the
AI hype. Our goal today, Let's try to cut
through some of that noise. Find the really important
takeaways for developers trying to figure all this out.
Exactly. It's less about the hype and
more about, well, understanding the real shifts.
What skills do we need now? What's the actual reality for
developers on the ground today? OK.
Good. Let's maybe start with some
data, because we've all seen those headlines, right?
Things like developer job openings dropping sometimes like
25%, that really feeds this narrative that AI is just gonna,
well, replace programmers. Right.
And here's where it gets really interesting.
Hmm, yes, there's a noted drop looking ahead to 2025, but it's,
it's way more complex than just AI taking over.
You have to think about other factors too, like how we even
define roles, computer programmer versus software
developer. That's changing.
Plus there's the whole post pandemic market correction, you
know, after that hiring frenzy and things like remote work
outsourcing, that's still a big trend.
So it's not just one thing. AI is having an impact,
definitely, but it seems focused on a certain, let's say, type of
development work. The developers who are really
thriving, they're the ones committed to constantly
learning, adapting, which ironically, Jenny, I can
actually help with. It makes that path easier in
some ways. Adapting that brings up new ways
of working, doesn't it? And maybe some new risks.
I know the author Mario Bittencourt talks about this
idea of vibe coding underage. Karpathy coined it.
I think it's become super popular, that phrase.
But what does it actually mean? Yeah, that's a great point.
And we need to be careful about what some call semantic
diffusion, you know, where a buzzword just kind of loses its
original meaning. Vibe coding, really.
At its core, yeah, it's about sort of surrendering to the AI,
just blindly accepting what it spits out, fixing things with
more prompts instead of digging into the code yourself.
Mario Bettencourt suggests. Maybe it's OK for like, quick
throwaway projects, yeah, or maybe when maintainability,
security, those things aren't top priority.
But otherwise, yeah, it feels a bit irresponsible.
OK, so if vibe coding is maybe not the best path for serious
projects, how do developers navigate this effectively?
What tools, What strategies should we actually be using to
partner with AI? Well, it's kind of surprising is
that a lot of developers still aren't really using Gen.
AI tools day-to-day. The keys really integration.
You need to pick a tool that integrates Gennai well.
Could be Cursor, Jetbrains, Vscode, Neovim.
Lots of options are emerging. The main thing is use them.
Learn what they can do, but also critically what they can't do
well. Right, understand the limits.
Absolutely, and use the features within your IDE.
That chat function especially when it knows your code context.
Very useful code completion too. That tab tab tab thing.
It's great for quick local changes.
Then you have multi edits for bigger stuff across files where
it suggests changes you confirm and the most powerful perhaps
are the agents. Agents.
What are those exactly? Think of them like more
autonomous helpers. They can handle multi step tasks
like creating a whole new feature, updating existing ones,
even bootstrapping an entire application based on commands.
Super powerful, but you have to stay in the driver's seat.
Always be in control. These tools sound amazing,
almost transformative, but how do we get the absolute most out
of them without, you know, falling into that vibe, coding
trap or other pitfalls? Crucial part, isn't it?
It's not just about installing a plugin, it's about how you use
it. So maybe three key tips here.
First, contest is absolutely king.
Don't just give vague prompts, be specific.
Provide versions, documentation, links.
If you can guide the AI, reduce those hallucinations.
Makes sense. Garbage in, garbage out still
applies. Pretty much, yeah.
Second, define your standards up front.
You can actually set up instruction files in your IDE,
Tell the AI you're coding standards, project structure,
security rules. You could even ask the AI to
look at your code and help define those standards for.
You oh interesting, using AI to teach the AI about your project.
Exactly. And 3rd, find balance breakdown
big tasks. If you give the AI a huge spec,
it might struggle. These models tend to remember
the beginning and end of a conversation best.
So break it down. Bootstrap first, then maybe you
work feature by feature, then refactor.
Smaller focused interactions work better.
OK, so we've gone from tackling those job loss fears to some
really practical ways to integrate.
Jenny. It really sounds like the craft
of development is evolving rather than just vanishing.
Absolutely. I mean, just ignoring Jenny I
and its potential value, not even trying it out periodically,
that seems misguided. But blindly trusting everything
it generates is just as risky. The future here.
It's really what you decide to make of it, how you choose to
adapt. The powerful thought to end on
adaptation is key. For more details on everything
we discussed today, do check the description.
And please don't forget to subscribe.
It's free to the Architecture Corner newsletter over at
architecturecorner.substack.com. Thanks so much for joining us.