LongCut logo

How To Learn To Code In 2026

By Tina Huang

Summary

Topics Covered

  • Agentic Engineering Replaces Vibe Coding
  • Master Architecture Over Code Details
  • Git Prevents AI Coding Disasters
  • Containerize to Isolate AI Chaos
  • AI-Primed Projects Accelerate Mastery

Full Transcript

Learning to code is so different in 2026. So, in this video, I shall explain

2026. So, in this video, I shall explain to you how to learn to code in 2026.

Starting off with what coding actually looks like today. It looks very different. Then, I'll explain what you

different. Then, I'll explain what you should be learning that is still relevant right now and for the future.

And finally, some tips on how to supercharge your learning. Oh, by the way, just in case you have any doubt about whether you should still learn how to code in 2026, the answer is yes.

There are still so many opportunities that are only available to people who know how to code. Plus, learning to code in 2026 is so much easier and faster than it used to be. So, it's kind of a no-brainer if you want to build stuff.

Now, with that out of the way, in case you don't know me, hi, my name is Tina.

I used to be a data scientist at Meta, and I have been coding for 10 years.

Without further ado, let's go. A portion

of this video is sponsored by Warp. On

February 3rd, 2025, Andre Kaparthy, the previous director of AI at Tesla and the founding member of OpenAI, made a viral tweet defining a new term called vibe coding. He explains, "There's a new kind

coding. He explains, "There's a new kind of coding I call vibe coding, where you fully give into the vibes, embrace exponentials, and I forget that the code even exists. It's not too bad for

even exists. It's not too bad for throwaway weekend projects, but still quite amusing." Then almost exactly a

quite amusing." Then almost exactly a year later, on February 5th, 2026, he made another post. Today, one year later, programming via LLM agents is increasingly becoming a default workflow for professionals, except with more

oversight and scrutiny. Now to

differentiate this much more sophisticated integral workflow from vibe coding. He said his current

vibe coding. He said his current favorite term for it is agentic engineering. You have your terminal/ ID

engineering. You have your terminal/ ID open where you have multiple coding agents coding furiously away for you and you're like build this fix this. No,

don't do that. Do this instead.

Orchestrating your AI agents like a puppet master. But do not be fooled. It

puppet master. But do not be fooled. It

may look like you're just speaking English to the AI agents and just like orchestrating them. But you need to be

orchestrating them. But you need to be an experienced software engineer to even do that. You need to know how to

do that. You need to know how to structure what it is that you want to build in a way that the AI agents can understand. Be able to provide context

understand. Be able to provide context and documentation. And in order to

and documentation. And in order to correct the AI and tell it that it's wrong, you need to actually know what is right. To be a good manager, you need to

right. To be a good manager, you need to know what it is that you're managing. So

that is why if you want to learn how to code in 2026, you still need to know the fundamentals of coding and engineering.

But instead of focusing so much on the details of the code implementation itself, it's about understanding big picture software design, systems, and architecture. and particular emphasis on

architecture. and particular emphasis on security and privacy because these are the things that AI coding agents tend to struggle the most with. Then you can actually move on to take advantage of the AI coding tools that we have

available today and really do agentic engineering. So shall I tell you what it

engineering. So shall I tell you what it is that you need to learn? All right,

I'm going to list out the topics in a roughly chronological order that I think you should be learning assuming you don't know anything and also suggest some resources on these topics.

Okay, so first thing that you want to learn is the basics of coding itself.

stuff like variables, types, if statements loops object-oriented programming, and APIs. Also, I'm using Python as the demo language to learn, which is particularly good if you want to be building AI agents and doing data

stuff. But if you want to be doing

stuff. But if you want to be doing something more like web stuff, like developing web apps, you might want to start off with a language like JavaScript. It's okay though because I'm

JavaScript. It's okay though because I'm going to give you guys a prompt at the end of the section that you can use to customize this learning plan specific to the language of what you want to be learning. Okay, great. So, these are the

learning. Okay, great. So, these are the basic basics. Like you really need to

basic basics. Like you really need to know these otherwise you wouldn't even be able to read the code that the AI generates.

>> That sign can't stop me because I can't read.

>> And I'm going to put on screen now some of my favorite resources on this topic.

I personally still recommend going with these humanmade resources uh because we know that they're really good. They've

been invented by thousands of engineers.

Besides all AI generated code is based upon code that was written by human developers for decades. Next up you need to learn about software architecture.

What that means is how is it that projects are structured? How do you choose a tech stack, the system design, what kind of APIs should you be using, and how the data flows through your software and where is it being stored?

What kind of databases are you using?

And testing. Testing is so important, especially if you're using AI coding agents. You need to understand how to

agents. You need to understand how to write test cases and how to test different parts of your software. And

finally, how does deployment work? Where

are you going to be hosting your software? This is like the bread and

software? This is like the bread and butter of software engineering. And you

really need to understand these highle things to be able to direct your AI to be building the things that it should be building and redirecting it when it's doing something wrong. You need to be able to conceptualize what the end

product should look like based upon the requirements that you have. For example,

at work, you might want to build a software um that stores a massive amount of information and have lots of people querying it all the time. So then you need to be thinking, what sort of database should I be using that is cheap, safe, and fast? And how do I

design a user interface that allows for multiple people querying at the same time? These are all like design

time? These are all like design questions that you need to be able to understand. I'm going to put on screen

understand. I'm going to put on screen now some resources that you can check out to learn about these topics. Next up

is version control and GitHub. By

version control, we mean a system that's able to track the changes in your files and code over time. So you can track the history, revert back if you need to, and collaborate simultaneously with other people as well. There are actually a lot

of different types of version control software out there. Um the most popular one is called Git. So people would use Git in order to do version control and then put their code on something called GitHub. GitHub is industry standard for

GitHub. GitHub is industry standard for displaying your code, sharing it, and collaborating with other people. This is

especially important if you're intending to do agentic engineering because you want to be tracking the changes that your AI coding agent is doing, right?

And in case it makes a mistake, you can revert it and redirect it without like losing your entire codebase, which by the way, this happened to a lot of Vibe coders who did not know the fundamentals of coding and engineering. I'll put on

screen out some resources for you to learn about version control and GitHub.

All right, next up is security and privacy. So this is a topic that was not

privacy. So this is a topic that was not particularly important when somebody is learning how to code um like a few years back like obviously security and privacy is important right but it's sort of something that just gets taught like

within the scope of other things like how does authentication work and how do you like integrate authentication into your apps but the reason why I'm separating this out as its own like little topic here is because I think it's particularly important in this day

and age to learn about security and privacy because it's usually one of the blind spots of AI coding agents. So you

as the human can't just kind of like hope that the AI agent is just going to take care of it. You do need to be quite explicit in incorporating these principles. Don't worry, this is

principles. Don't worry, this is honestly not like a really big topic.

It's just really important to know. And

as they say, I think paranoia makes a good engineer. Maybe I'm going to put on

good engineer. Maybe I'm going to put on screen now a few different resources that I suggest you take a look at and learn about privacy and security. All

right. So at this point, you would have covered pretty much the fundamentals of coding and software engineering. Now,

you have now earned your stripes to be able to harness the power of agentic engineering by using AI coding agents.

Yay. But with that being said, I do want to throw in a bonus little topic which is debatable whether it's actually like necessary necessary for you to know this topic, but I personally think it's pretty important and you're probably

going to have to learn about it anyway.

And that is microservices, otherwise known as the concept of containerization. This is a software

containerization. This is a software deployment method that packages an application's code together with all of the files, libraries, and dependencies that it needs in order to run that piece of code. So, it's sort of like little

of code. So, it's sort of like little packages, little containers of pieces of software. The purpose of this is to

software. The purpose of this is to isolate the application from its surroundings. So, it's not interacting

surroundings. So, it's not interacting with the rest of your computer. Um, and

it's able to run consistently across different computing environments like different computers, different computing systems, different types of clouds. This

is usually more of an advanced topic and people usually learn about this when they're building stuff or like on the job. But the reason why I'm putting this

job. But the reason why I'm putting this here as like an optional but maybe you should learn about this kind of topic is as another precaution if you're using AI coding agents. You can imagine if you're

coding agents. You can imagine if you're letting your coding agent or even like multiple coding agents just do whatever it wants, right? It can end up messing up your development environment entirely or like building things in a way that cannot be properly deployed and used by

other people and you'll be just left like really frustrated cuz you can't figure out why it's happening. So if you do take the precaution to containerize, you're going to end up with something more reliable. And if your AI agent does

more reliable. And if your AI agent does run a mock and starts doing crazy things, it's going to be in its own little environment doing it. So worst

case scenario, just shut off that environment. Let me know in the comments

environment. Let me know in the comments of these topics I have just covered. How

many of these topics do you already know? Which ones do you still need to

know? Which ones do you still need to learn? Curious where you guys at on the

learn? Curious where you guys at on the learning journey. As promised, I'm also

learning journey. As promised, I'm also going to put a prompt on screen. also

probably link in description too which you can put into your favorite AI chatbot. ChachiPT, Gemini, Claude, Quen,

chatbot. ChachiPT, Gemini, Claude, Quen, Deepseek, whatever you want and it will help adapt this learning plan and resource list to fit the goals of your learning and also help you determine which coding language makes the most

sense for you to learn. Yay! Amazing.

You have now earned your stripes to be able to tackle this new world, this brave new world of agentic engineering.

Now, agentic engineering itself, gosh, it just agentic engineering does not sound as cool as vibe coding. It's just

not as catchy. It's fine. Agentic

engineering, okay, agentic engineering itself is also a skill. It involves how to set up your project and how to set up your AI coding agents, how to communicate what it is that you wanted to build to your coding agents, and how

to monitor them correctly, among many other things. For agentic engineering,

other things. For agentic engineering, there are different options for which coding agents to use and how to use them and orchestrate them together. Me

personally, I really like using Warp, who is also the sponsor of this portion of the video because it's a prodeveloper tool that covers the full spectrum of AI coding. Getting started is so simple. I

coding. Getting started is so simple. I

built this entire project using Warp.

But as it scaled, I needed to move faster, and that's where the magic begins. Instead of tackling one thing at

begins. Instead of tackling one thing at a time, I deployed multiple coding agents simultaneously. Here's one that's

agents simultaneously. Here's one that's adding a back-end feature, one on documentation, and one that's writing tests. This is all powered by Oz, which

tests. This is all powered by Oz, which is a cloud-based agent orchestration platform built on top of WR. The Oz

dashboard gives you a real-time view of all your agents. At a glance, you can see what they're working on, their status, and any issues that they may have. And because it's cloud-based, each

have. And because it's cloud-based, each agent runs in its own isolated environment, meaning that they won't interfere with each other, and my poor MacBook Air can stay alive. That is not all. You can actually incorporate Oz

all. You can actually incorporate Oz within your project itself. For example,

this is a scheduled agent that updates my micro site every day. It goes in there, takes AI news of that day, which is what I care about, and summarizes it and displays that information for me.

With Oz, you can also convert skills into AI coding agents, integrate them directly with Slack and Linear, and tap into a ton of other features that support team workflows. 700,000

engineers are already using it, and 97% of code diffs get accepted, which honestly is pretty impressive and tracks from my experience, too. So, if you want to get started, you can get started for free at the link linked below. Thank you

so much for sponsoring this portion of the video. Now, back to the video.

the video. Now, back to the video.

Unfortunately, there are not that many good resources on agentic engineering.

Probably because it's such a new topic, but I'm going to put on screen now a couple videos that I've done and some other resources as well. If you guys want, I can also make a video that specifically covers how to do agentic engineering. You know what's crazy is

engineering. You know what's crazy is that to learn all of these topics that we just discussed prior to AI, it would have taken you years, like people go to school for this and then work multiple years to get to this level or even if

they're attending like a fasttrack boot camp, we're still talking like at least 10 to 12 months completely full-time.

But with good learning techniques and with AI to help with your learning, you can reduce the learning time down by so much. I think that if you really focus

much. I think that if you really focus and say you're doing it like completely full-time, I would estimate maybe like 6 months to be able to learn all these topics very solidly. So, in the next section, I'm actually going to share some of my favorite learning techniques

that can help you learn faster. For

those of you who watched my channel for a while, you probably also know that learning things fast is like my favorite activity. So, very exciting. Let's now

activity. So, very exciting. Let's now

talk about tips to supercharge your learning.

I'm going to divide these tips up into two different categories. The first is how to use your resources better like the lectures, the books, and the second is how to use projects for learning and specifically how to use a AI coding

agent to help you build a project and learn at the same time. Two birds with one stone. Okay, let's first talk about

one stone. Okay, let's first talk about how to use resources. If your resource happens to be like a video or like some text or like readings and stuff like that, I would really recommend using something like notebook LM and put all

that information in there and ask it to summarize things for you and also to generate questions that will guide you along the work. This is called priming and can really speed up your learning process because you'll understand what

are the things that you need to be learning and how they fit together with each other. As you're going through the

each other. As you're going through the lectures, the text and like code snippets and and whatever. Um, if

there's anything you don't understand, you can also just copy paste that and put that into AI to help you explain what's going on. When it comes to code and logic, at least of the filming right now, the best AI model to do this would

be Claude. I personally default to using

be Claude. I personally default to using Claude Sonnet for anything that happens to do with code. But if you don't want to pay for it and you run out of the free trial, honestly, most modern AI models would be able to help explain code. You can even use the free ones,

code. You can even use the free ones, the open source ones like Quen, Kimmy, or DeepSync. Another way that I really

or DeepSync. Another way that I really like using AI models to help me learn is by taking a concept and ask it to give me examples and analogies because this will really allow it to solidify in my mind to understand the concept. Like for

example, if you're learning about object-oriented programming, you can ask it explain object- oriented programming to me using analogy and provide examples much clearer I think. And finally,

oftentimes the best way to learn how to code is to take the code and the snippets from the resources that you have like other people's code and then ask AI to help you understand the code

that's there to explain to you what the code is doing. This is so powerful and I'm kind of salty that I did not have this option when I was learning how to

code. To do this, you can also just like

code. To do this, you can also just like copy paste or like upload the code into an AI model or this could be a good opportunity for you to set up an AI coding agent. just give it the code and

coding agent. just give it the code and it would explain to you the structure of the code, how the pieces are fitting together, um what different lines of code mean line by line if you want. And

speaking of projects, this is a good transition to the second category of tips that I have, which is for projects.

First of all, I want to just emphasize that projects are the best way for you to learn how to code. Hands down. You

can watch like so many lectures, read so many things and whatever and you think that you know these things. Yeah, but

you don't unless you actually start building with it. And the way you do that is by doing projects. So I

encourage you to do projects continuously as you're learning. Like if

you're learning about how to use an API, actually make a project in which you use an API or multiple APIs. If you're

learning about testing, write some tests. Try to understand the differences

tests. Try to understand the differences between different tech stacks, try them out yourself, especially with the help of AI coding agents. It is so easy to do this. You can ask the coding agent

this. You can ask the coding agent something like build me a music storage software with like XYZ specs built with a Django backend, a Nex.js JS front end and store the data in a SQLite database

for example. This how you're going to

for example. This how you're going to learn faster, gain more experience and also work towards um using AI coding agents with agentic engineering. I

previously mentioned other people's projects as well. Another great way for you to learn is to take other people's projects and then adapt them. Add on

more stuff to them. Change around the code and see how the results change.

This is such a great way to learn and a staple amongst engineering students everywhere. Another tip, as you're

everywhere. Another tip, as you're coding, you can also ask AI to give you multiple suggestions for how to implement something. This way, you can

implement something. This way, you can expand the skill of your knowledge, which is going to make you a much better coder. And final little tip, ask AI to

coder. And final little tip, ask AI to help you understand documentation. I

hate reading documentation. Like, I hate it so much. I don't think I've read any documentation since like 2024 cuz I will ask AI to help me understand documentation. To be clear, I still need

documentation. To be clear, I still need to understand the documentation. I just

don't like reading it. So, this is a great way to understand documentation faster and incorporate them into your projects. I'm not going to go into vibe

projects. I'm not going to go into vibe coding/ aentic engineering specific tips right now because there's just like way too much and there's a whole other video that I can make on this topic. So, I'm

just going to put on screen some of my favorite little vibe coding tips. If

that's helpful for you guys, just know that this is not everything and it might be confusing if you've never had any experience at all. Let me know in the comments if you want me to actually make like a fullyfledged video uh for that

topic. All right, we have now come to

topic. All right, we have now come to the end of this video. Thank you so much for watching until the end. I know that was a lot. I really hope this is helpful to you. I'm so glad that you're learning

to you. I'm so glad that you're learning how to code in 2026. Best of luck in your coding journey and I will see you guys in next video or live stream.

Loading...

Loading video analysis...