A New Take on AI

I came across a great video with a new take on the inclusion of AI or agentic coding in software engineering. The creator had a refreshing take on things that seemed to see a more positive viewpoint.

So, most annoyingly I can’t seem to find the video that I got these points from, but it was so good that I just had to share these points. I have been looking for the video for ages and so these points were gathered a few weeks ago. Hopefully, some of it is still useful although the tone about AI in coding has changed a lot now, but I still wanted to record these almost as a reminder.

[If I find the video I will update this post.]

So below are the points the video writer made and I just wanted to share a few of my thoughts on them.

The fear of AI taking things over

Instead of seeing AI or agents as a tool, people were getting hung up on it simply taking their jobs and doing everything. As with every new piece of tech there is always a transitional period, which we’re living in, before a new normal settles. We don’t know what that will look like, but it may not look that different to what we have now. Agents doing the bulk of the writing and reviewing, engineers doing the design, planning, and creative input (not to mention applying guardrails).

The idea of shipping code that noone is really checking

One of the fears of AI is the idea that code will be shipped without ever being checked. Interestingly, since finding this video we have had Amazon and others all have issues arise due to AI code being pushed out without proper human checks. It seems there might need to be a change in the way we review code or maybe how we PR code. See this article from Bernard at Lubeno.

Claude built the compiler, but it used GCC from decades ago and a whole team of engineers

A while back Anthropic announced that an entire C compiler had been vibe coded with Claude, it rocked the internet. But this video made the great point that it still require GCC, that was made decades ago in 1987 and require a whole team of engineers holding Claude’s hand and guide it along.

Software Engineers being replaced and software shares dropping in price, but software companies are hiring

Even though there is all this talk about AI replacing engineers, and some of the bigger companies laying people off. Their stock prices and valuations are dropping, and yet a lot of SaaS companies are actually hiring more engineers. It’s a strange situation and I honest don’t know what it means, but it was interesting to note non-the-less.

Basic coding stuff, CRUD, entry level eptititon, boiler APIs, tutorial projects, AI can do it easy

This is one of those places where we should definitely be leaning into AI. They can produce all of the boilerplate, base setup and scaffolding parts of an app without any engineer wasting any time. While an AI is doing that an engineer can be making important designs about the design of the app.

Prod bugs, security reviews, performance disasters these need people

There is still a few scenarios where a human is needed. These situations need someone to shoulder the risk but also to take the blame. Leaving these things in the hands of a machine risks missing so many nuances and also I imagine makes investors uncomfortable with their investments if they feel ‘no one’ is working/monitoring it.

Reviewing code, fixing failures and issues, managing the system and the risk

Most of the models are still not great at correcting and writing code in an optimal way, they can be quite verbose. And this is another area where an experienced engineer can point it in the right way. Again managing the risks and making the decisions that affect the future trajectory of the app fall on the shoulders of the engineer.

Not about typing fast about thinking deeper.

The future for engineers is not about typing fast or writing X lines of code in a day, it becomes about thinking deeply and being able to analyse situations and determine the best way forward. This might be with the help of the AI but the final decision will be made by an engineer.

We are AI superviors who question and reviews

It may become that we are essentially supervisors to agents working on the code. This will suit some but not others. Some don’t want to manage, or have the skills to manage. This may change the industry and be one of the true sources of job change in the industry.

AI needs devs more than devs neeed AI.

The end point was that AI need devs more than devs need AI. A truly competent and experienced developer who is capable of thinking deeply, managing other engineers and agents, and also to make the right calls about the right framework, tool or module for the right situation is much more valuable than the AI agent.

It’s an exciting time, and also still a bit scary, things are changing fast and it can feel like we might get left behing if we don’t keep up. I think these points give us some key things to keep our sights on. Working on our analytical and evaluation skills, keeping our interpersonal, leadership and management skills sharp, as well as being well read on the current technology (not AI, but frameworks, tools and patterns that are driving forward innovation).

Hopefully, you found something of use in here.

Until next time.