First time here?
Your first day with ABCsteps.
If "AI engineering curriculum" feels intimidating — if you have never written code, never used a terminal, never opened GitHub — you are exactly who this page is for. This is the gentle path in. Read what is here, breathe, then start with Lesson 01 below.
Common fears, named
The reasons you think this is not for you, addressed.
Most of the people who would benefit from this curriculum talk themselves out of starting. The reasons are predictable. Here is the honest answer to each.
"I am not from a science background"
You do not need PCM, calculus, or a CS degree.
The curriculum starts at "what is code" in lesson 01. No mathematical prerequisites. No physics, chemistry, or biology assumed. Commerce, arts, humanities students complete this every year.
"I have never coded before"
Lesson 01 explicitly assumes zero prior coding.
You will use an AI coding assistant to scaffold real code while learning what the tool is doing. By lesson 03 you will have built a small browser game. The "never coded" state is the starting state.
"I have a full-time job / college and no time"
The curriculum is calibrated for 5–8 hours per week.
One lesson per week is a reasonable pace. Twenty lessons = roughly twenty weeks at one per week, or three to four months at two per week. Most learners study evenings and weekends. No 12-hour days required.
"I am too old to start"
There is no age cap on engineering.
Working professionals, career switchers in their thirties and forties, and parents returning to work all complete this curriculum. The market does not refuse capable engineers because of birth year.
"My English is not great"
You can read the lessons in your own time.
The lessons are written in straightforward English. Read at your own pace. WhatsApp Q&A with Divyanshu (in the paid Job-Ready Track) can happen in English or Hindi. Engineering vocabulary is universal — the lessons explain every term before using it.
"I cannot pay 4,999"
The entire curriculum is free to read on this site.
Twenty lessons, thirty articles, the glossary, the reading paths — all publicly readable, no signup, no email gate. The Job-Ready Track is optional for those who want videos and direct support. The learning is genuinely free.
Your first 30 minutes
A concrete first half-hour with this curriculum.
The hardest moment in learning anything is the very first action. To make that easier, here is a specific, time-boxed first 30 minutes you can do right now without installing anything, without paying anything, and without any prior knowledge.
0:00 – 0:05
Read
Read the homepage and the why
Open the homepage and the /why-abcsteps page in two browser tabs. Read both. Five minutes. The goal is to know what this is, what it is not, and whether it fits you.
0:05 – 0:15
Open
Open lesson 01 — AI-Assisted Code
Click into the first lesson. Read the "Before You Study" section and "The Concept" section. Do not try to do anything yet. Just read what the lesson is about. Ten minutes.
0:15 – 0:25
See
Open Antigravity (the AI IDE the lesson uses)
In a third browser tab, go to the Antigravity site and open the editor. You do not need to install anything; it runs in the browser. Type a one-line question into the chat. Watch the response. You have just done the thing engineers do every day in 2026.
0:25 – 0:30
Decide
Decide if you want to continue
Five minutes of honest self-reflection. Was that interesting? Could you see yourself doing more of it? If yes, continue with the rest of lesson 01 and the lab. If no, that is also useful information — engineering is not for everyone, and finding out cheaply is better than finding out after spending lakhs on a degree.
That is the first 30 minutes. If you got through them, you have already done more engineering work than most people who say they want to learn AI.
The rhythm
How a serious learner studies this curriculum.
The curriculum is calibrated for a sustainable pace. Not "complete in 30 days" hype, not 12-hour days that burn you out — a working rhythm a person with a job or college schedule can keep for months.
- 01
One lesson per week
Aim for one lesson per week as the steady pace. Some weeks you will do more; some less. The goal is consistency over speed.
- 02
Read first, build second
Read the entire prepare.md before you touch any tool. The reading is fast; the building is slow. Doing them in the right order saves hours.
- 03
Build the lab even badly
Each lesson has a lab. Do it even if your version is uglier than the example. A bad version of the project teaches more than reading three more lessons without building.
- 04
Review at the end
Read the review.md. Try the quick quiz. Skim the bonus challenge. The review locks the lesson into long-term memory and points you at next steps.
- 05
Repeat for 20 weeks
Twenty lessons at this pace = roughly five months. Five months is a real chunk of time, and the result is a portfolio of working projects you can show.
When you get stuck
Getting stuck is not failure — it is the work.
Every working engineer gets stuck. The skill is not avoiding stuck-ness; it is having a routine for getting unstuck. Here is the routine to use as you go through the curriculum.
Step 1
Re-read the section
Most "I am stuck" moments are "I read too fast" moments. Go back, read the paragraph again with fresh eyes. Often that is the entire fix.
Step 2
Search the exact error
Copy the error message verbatim and paste it into Google or an AI assistant. Engineers do this constantly. It is not cheating; it is the work.
Step 3
Sleep on it
If you have spent more than 30 minutes stuck on the same thing, stop. Come back tomorrow. The brain solves problems while you sleep more reliably than another hour at the keyboard.
Step 4
Read the related blog post
Many lessons have a companion blog article (linked in the lesson). The article often explains the concept from a different angle. The angle that clicks is the right one.
Step 5
Skip and come back
You are allowed to skip a hard step temporarily, finish the rest of the lesson, and come back. Sometimes the rest of the lesson contains the missing piece.
Step 6
Ask the WhatsApp Q&A
If you are on the Job-Ready Track, use the direct line. Tell Divyanshu what you tried, what happened, and what you expected. Specific questions get specific answers.
The Job-Ready Track adds direct WhatsApp Q&A with Divyanshu as part of the bundle. That is the optional fast-track for getting unstuck. The free path uses the routine above plus the broader internet — perfectly viable, just takes a little longer to find the right answer.
Three things to remember
The mindset that gets you to lesson twenty.
Show up, not understand everything.
You will not understand 100% of every lesson on the first read. That is normal. The goal is not perfection on day one — it is showing up consistently. Concepts you do not get in lesson 03 will click in lesson 07.
Build, do not just read.
Every lesson has a lab — a thing to actually build. Reading the lesson without doing the lab is like watching swimming on YouTube. You learn by doing the thing the lesson describes, even badly.
Slow is fine. Stopping is not.
A learner who does one lesson per week for 20 weeks will outpace someone who does ten lessons in a weekend and then quits. Steady beats sprint. The curriculum is calibrated for steady.
Ready
Lesson 01 is right here. The first action is one click away.
You have read this page. You know what to expect. You know the rhythm. You know what to do when stuck. The only thing left is the first click.