Nathan Sebhastian NewsletterSubscribe
← All issues

3 min read

Successful Developer Trait #2: I’m Patient and Smart Enough

Letting AI finish your projects won't get you hired. Be patient and learn to code the hard way.

Originally sent in December 2023 as an email course. Updated for 2026.

Hello again,

It’s wonderful to see you’re still here. I’m grateful that you decided to stick around.

Here’s trait #2 of a successful Software Developer:

I’m Patient and Smart Enough

Recently, I talked with a student planning for an internship. He learned JavaScript from a free online course, and he ended up finishing a challenge using AI and feeling not learning anything new.

He read every line of code but still feel like not knowing anything.

I encouraged him to write the code himself first, and only then ask AI for help. He said, ‘But I have developed a skill prompting AI to get the desired result.’

I stopped replying because I don’t like convincing other people that they are wrong. If they believe what they’re doing is right, then who am I to judge?

I bring up this issue because I want you to see things from the employers’ perspective. If you earn a certificate acknowledging that you have finished a JavaScript course, and then you apply for a position in the company, you would be interviewed when your resume gets their interest.

Next, the interviewer asked you about the project, and then you said how you finished that project with the help of AI, and you don’t learn anything from the project.

What do you expect? Do you think the interviewer’s gonna say, ‘Wow! Great job using AI to finish the task. You’re hired!’

When you sign up for a Marathon, you don’t call a Taxi to take you to the finish line. It’s the same way with coding. You don’t tell AI to finish your project and call yourself a developer.

And this matters even more today. Interviewers know every candidate has access to AI, so they look for the one thing AI can’t give you: understanding. Expect to be asked to explain your code line by line, debug it live, or change it on the spot. Even Anthropic, the company behind Claude, still tests engineers on writing, running, and debugging code. I covered their interview process in Has AI replaced software engineers?

Use AI to learn, not to skip learning

Now, I’m not telling you to avoid AI. In 2026, that would be bad advice. AI is part of the job, and it can make you learn faster. The difference is whether AI is doing the thinking for you or helping you think.

Here’s how I’d use it while learning:

  • Write it yourself first. Then ask AI to review your code and point out what you missed.
  • Ask for explanations, not solutions. “Why does this loop run one extra time?” teaches you more than “fix my code.”
  • Turn off autocomplete when practicing the basics. You can turn it back on once you can write the code without it.
  • Read every line AI gives you. If you can’t explain it, you’re not done.

I get it. You want to finish school and bootcamps as quickly as possible to get a job, but please understand that wanting to have a job quickly prevents you from having a job at all.

Back in school, I learned that teachers have a sixth sense to detect who cheats on their exams. They deal with students every day at work, how can they not?

It’s the same with interviewers. They have a sixth sense to detect who’s lying on their resume, trying to make themselves look good.

I have a friend who works at Human Resources, and while she doesn’t know how to create React applications, she has interviewed enough developers to know when one is lying.

And it’s not just her. Senior developers who are tasked with interviewing candidates have done many interviews. If they hire the wrong person, their job would be impacted. They have every incentive to weed out cheaters.

So what to do? It’s simple really. Be patient as you learn how to code. Take the hard way, because everyone’s taking the easy way out. When everyone go left, you go right.

I assure you, you are smart enough to complete those courses or bootcamps. You just lack the patient to do it in the right way. Stop hurrying.

I’ll see you in the next issue with the third trait of a successful developer. If you have any questions, just reply to the newsletter email.

Talk to you soon,

Nathan

More issues

  1. 4 min read

    REA: can AI really clone any app?

    I tried REA (Reverse Engineer Anything) to clone a desktop diagram app with Claude Code. Here's how it works and what it means for software.

  2. 4 min read

    Run Claude Code for free with Ollama

    How to connect Claude Code to local or cloud open models with Ollama, and what to expect from each.

  3. 5 min read

    Has AI replaced software engineers?

    93% of developers use AI, but productivity is only up about 10%. Here's what the data says about the "coding is dead" claim.

Subscribe to Nathan Sebhastian Newsletter

I'll email you about new tutorials, books, courses, software, building products with AI, and the projects I'm working on.

Free, unsubscribe anytime.