Zero to Full-Stack in 6 Months: The Izzy Way...

Israel Santana (Izzy) — Wed, 20 May 2026 14:20:30 +0000

TL;DR

This post is adapted from my 2024 YouTube video, "Learned To Code In 6 Months!". Since the original recording, I have evolved as a developer and expanded my technology stack beyond the initial scope discussed here.
Dedicated 6 months to studying full-stack development, Monday through Friday, 6:30 AM to 4:00 PM.
Managed distractions using the Pomodoro technique and physically removing my phone from the workspace.
Learned almost entirely via free YouTube tutorials, avoiding "tutorial hell" by actively building.
Built a complex first project ("Nissan Experience") to force hands-on learning.
Leveraged AI (Gemini) as a mentor for concept breakdown, alongside real-world guidance from Dorian (@doriandevelops).
Maintained mental health through strict weekend breaks, attending NYC Code & Coffee meetups, and heavy weightlifting.

Greetings from the future. This is Izzy, writing to you from the year 2026. The following article is a time capsule detailing exactly how I learned full-stack development in just six months back in 2024.
_

My name is Izzy, and over the past six months, I executed a dedicated roadmap to learn full-stack development. This is not a heavily edited, polished fairy tale. It is an objective breakdown of my schedule, the technologies I adopted, the struggles I faced, and the strategies that kept me disciplined.

1. The Study Schedule and Discipline

Creating a routine puts discipline on autopilot. My standard study schedule was Monday through Friday, 6:30 AM to 4:00 PM. On the three days a week I went to the gym focusing heavily on progressive overload for my chest, shoulders, triceps, and legs, I concluded my study sessions at 3:00 PM.

Rigid Study Schedules

Pros: Automates decision-making; guarantees a high volume of deep work; sets clear boundaries between "work" and "life."
Cons: Can induce severe guilt when life inevitably disrupts the routine; high risk of burnout if breaks are not strictly enforced.
Potential Pitfalls: Confusing "hours logged" with "actual learning." Staring at a screen for 9 hours is useless without active coding.
Conclusion: A rigid schedule is necessary, but it must be paired with mandatory time off. I absolutely do not study on weekends, forcing myself to step away and reset.

2. Environment Architecture: Beating Distractions

To combat context switching, I removed my phone entirely, placing it across the room and relying on an Apple Watch strictly for critical alerts. For desktop distractions, I implemented the Pomodoro method using an always on top window timer.

The Pomodoro Technique

Pros: Forces regular breaks to prevent cognitive fatigue; gamifies deep work; prevents endless scrolling.
Cons: Can arbitrarily interrupt a deep "flow state" right when a complex bug is being solved.
Potential Pitfalls: Becoming a slave to the timer.
Conclusion: The structure is invaluable for maintaining focus over an 8-hour day, provided you allow flexibility when deep in the zone. Listening to synth-wave Lo-Fi music (like Lo-Fi Girl) also served to anchor my focus without the distraction of lyrics.

3. Financial Reality

Transparency is critical. I am able to study full-time because of an agreement with my wife. For three years, I financially supported us while she completed an intense physician assistant program. Once she secured her role as a PA, we flipped the script, allowing me to quit my job and pursue software engineering full-time.

4. Resource Allocation and "The Izzy Stack"

I learned 99.9% of my foundation through free YouTube tutorials, starting with HTML, CSS, and a comprehensive "50 Projects in 50 Days" vanilla JavaScript course.

Fast forward to 2026, my learning path solidified into what I proudly call...

The Izzy Stack:

Frontend: React, TypeScript, Tailwind.
Backend: Java, Spring Boot, PSQL, Supabase.

Relying on Free Video Tutorials

Pros: Zero financial barrier to entry; diverse range of instructors and teaching styles.
Cons: Information is often fragmented, outdated, or lacks enterprise-level best practices.
Potential Pitfalls: Falling into "Tutorial Hell," where you passively consume content without writing your own code. If a 2-hour tutorial takes you exactly 2 hours to finish, you did not learn anything.
Conclusion: Tutorials are only valid if you constantly pause, break the code, and rebuild it yourself.

5. Mentorship and AI as a Learning Tool

Learning in a vacuum is dangerous. I reached out to Dorian (@DorianDevelops), who provided actionable, game-changing direction: stop doing tutorials, start building a full-stack project, and network immediately. I also utilized Gemini as a daily tutor to explain complex topics.

Using AI for Code Learning

Pros: On-demand, 24/7 explanations of granular concepts; excellent at breaking down documentation.
Cons: AI frequently hallucinates or suggests deprecated syntax; it can become a crutch.
Potential Pitfalls: Copying and pasting AI-generated code without understanding it, leading to a brittle codebase and failed technical interviews.
Conclusion: AI should be treated strictly as a mentor, not an employee. Never implement code you cannot personally explain from scratch.

6. Project-Driven Learning: The ("Nissan Experience")

Following Dorian's advice, I built a full-stack application as my first major project a tribute platform to Nissan vehicles featuring Stripe integration and a relational database.

Building a Full-Stack App as Project #1

Pros: Forces a holistic understanding of how APIs, databases, and client interfaces interact; generates a highly impressive resume asset.
Cons: The learning curve is brutal. Concepts like environment variables, Git workflows, and API security hit all at once.
Potential Pitfalls: Quitting out of sheer frustration when connecting the database or setting up authentication.
Conclusion: It took me three months and involved deep frustration, particularly with JavaScript logic, but the trial by fire approach accelerates true engineering comprehension better than building ten simple calculator apps.

7. Community and Next Steps

Coding in isolation breeds anxiety, especially given current market conditions. Finding a local community is non-negotiable. I consistently attend Code & Coffee in NYC, which has been instrumental in networking with data scientists, product managers, and fellow engineers.

Moving forward, I am limiting myself to three high-complexity projects this year, diving deeper into TypeScript, AWS, and eventually LeetCode. The market is tough for juniors, but the only controllable variable is the daily consistency of showing up.

🛠️ Let's Connect!

Website: callmeizzy.dev
YouTube: Call Me Izzy
GitHub: @MrItzreal
X / Twitter: @fullstackizzy
LinkedIn: Israel (Izzy) Santana

DEV Community: Israel Santana (Izzy)