AI//7 MIN READ

AI Is Scaring Me as a Developer — So I’m Learning to Work With It

AI is changing software development and the tech job market fast. Here's how I'm dealing with the fear of AI and learning to use it without letting it replace my thinking.

what am I even learning next?

I'm going to be honest. AI scares me.

Not in the “robots are going to take over humanity and we'll all be living in a warehouse” kind of way. I mean professionally.

I'm a developer. My job is, in very simple terms, to solve problems with technology.

And now we have tools like GPT-6, Claude and Gemini that can write code, explain code, debug code, generate ideas, read documentation, work through problems and produce something usable in a fraction of the time it used to take.

"“Okay... so where exactly does that leave me?”"
A glowing CRT monitor displaying retro green code in a dark room.

The tech job market already feels different

Getting a tech job was never easy. But it feels different now. There are more developers. More people learning to code. More bootcamps. More computer science graduates. More experienced developers looking for work.

And now there is AI making individuals dramatically more productive.

"“Will companies need as many developers as they used to?”"

That's a much harder question. And I don't think pretending it isn't happening is going to help us.

I used to think being good at coding would be enough

When I started learning development, I had a relatively simple idea of what I needed to do. Learn JavaScript. Learn React. Build projects. Get experience. Get better. Get paid more. Simple enough.

Except the industry doesn't stand still long enough for that plan to work forever. The stack changes. The tools change. The expectations change. And now the way we actually write software is changing.

I can open an AI coding tool and ask it to create a component that would have taken me considerably longer to write manually. I can ask it to explain an unfamiliar codebase. I can paste an error into a model and get several possible explanations within seconds.

So... am I trying to avoid AI?

Absolutely not. That would be like refusing to use Git because people used to upload files through FTP. Or refusing to use Stack Overflow because you think real developers should memorize everything.

The tool isn't the skill. And I'm slowly learning that my goal shouldn't be to compete with AI at producing lines of code. That's a losing game.

Instead, I want to become better at everything around the code. Understanding problems. Making decisions. Knowing when an implementation is wrong. Understanding users. Thinking about accessibility. Performance. SEO. Security. Architecture. Business requirements. Communication.

I'm learning to use AI as a teammate, not a replacement

This has probably been the biggest shift in how I work.

"Instead of: “AI, build my website.” I'm trying to think: “Here's the problem. Help me think through it.”"

I don't want to become the person who accepts whatever the model spits out because “it works.” Something working isn't the same thing as something being good.

The job market is making this even more frightening

There is another uncomfortable reality. Developers aren't competing only against AI. We're competing against other developers who are also using AI.

If I'm applying for a role and 500 other developers can now use AI to improve their portfolios, prepare for interviews, build projects and move faster... then simply saying “I know React” isn't going to carry the same weight it once might have.

  • Can I take a messy business problem and turn it into a working product?
  • Can I understand a client's actual needs?
  • Can I make a website fast? Accessible?
  • Can I look at AI-generated code and recognize that it shouldn't be shipped?

Maybe the real skill is becoming harder to replace

I don't know what the tech industry will look like five years from now. But I do know this: The industry is changing. The tools are changing. The hiring market is changing. The definition of productivity is changing.

I'm going to learn the tools. I'm going to experiment. I'm going to use AI to make myself faster. I'm going to learn what it is good at. I'm going to learn where it fails. And I'm going to keep developing the skills that require more than generating code.

Because I don't think the future belongs to developers who refuse to use AI. And I don't think it belongs to developers who blindly let AI do everything either. I think it belongs somewhere in the middle.

"People who can think + people who can build + people who know how to use the tools available to them."
my take ↓

Anyway, that's what I've been thinking about lately. Back to building.

From the archive

Read something else.