{
  "video_id": "7LeW1XLjeds",
  "channel_slug": "codewithantonio",
  "channel_handle": "codewithantonio",
  "title": "I don't build the way I teach",
  "duration_seconds": 538.0,
  "url": "https://www.youtube.com/watch?v=7LeW1XLjeds",
  "upload_date": "",
  "transcript": "All right, we are recording. I guess\nthis is some kind of a face reveal, even\nthough I did show myself a few times\nbefore. For those of you who haven't\nseen it, this is Code with Antonio. This\nis what I look like. I want to talk\nabout the way I make my YouTube videos\ntoday, things I can do to improve them,\nand something I've been working on for\nthe past 2 months. So, how would I make\na new video today? Well, it will all\nstart with me building it for myself\nfirst. In this first build, I decide\nwhat the architecture is going to look\nlike. I make the technical decisions\nabout the tech stack that I'm going to\nuse. I fix all of the bugs, all of the\nerrors. I do some refactoring if I hit\nsome dead ends. And then I package it up\nand I start rebuilding it for you on\nYouTube. With this method, everything\nthat I do when I record myself works on\nthe first try. That is because all of\nthe architecture has been predecided in\nthis first build that I did for myself.\nWhich also means that all of the errors\nand bugs are avoided. So essentially, if\nyou just copy what I do for the next 10\nhours, you will end up with a finished\nproject. Sounds good, right? Well, there\nare some obvious problems with this\nmethod, but they are what a lot of\npeople want to see on YouTube. They want\nto get from point A to point B. But in\nthe age of AI, this simply isn't as\nuseful as it might have been 3 years\nago. So, it's time to rethink how\ntutorial should look like. One way we\ncould fix this is instead of recording\nmyself rebuilding the project, I just\nrecord myself building it for the first\ntime with this method. I will inevitably\nget stuck and hit some kind of dead end.\nThen you're going to have to watch me\nmake some technical decisions to get\nout. Then I might encounter some errors\nand bugs and you will have to watch me\ndebug and refactor the project live on\ncamera. The outcome of this style of\nteaching is that you will understand how\nI think rather than understand what is\nthe next line of code in order to get\nfrom point A to point B. So a drastic\ndifference in teaching. Essentially\ninstead of code with Antonio you would\nlearn how to code like Antonio. This is\nan idea that I've had in mind for a long\ntime now but it's not really as simple\nas it sounds. If you thought my 20our\nvideos were long, wait until you hear\nthat this style of video would be 200 if\nnot even more hours long. That is\nbecause the reality of coding is not as\nstraightforward as my current tutorials.\nSometimes I get stuck for days and have\nno idea how to move forward. And there\nsimply wasn't any way that I could\npackage the reality of coding and\npublish it to YouTube without it being\nextremely long and honestly extremely\nboring as well. Or at least that was\ntrue until I started using AI in my\ndaily workflow. And two months ago, I\nmade this post where I quote unquote\nadmit that I've been using AI to write\n99% of my code. And just as I expected,\nit got varying reactions. Some people\ncould finally relate and explain their\nworkflow while others thought that this\nis a vibe coding and couldn't disagree\nmore. I want to show you a distinction\nbetween agentic coding and vibe coding\nbecause a lot of people mix the two.\nVibe coding is essentially only focusing\non the outcome rather than the technical\nspecification that goes into building a\nnew feature or an entire new app. You\nmostly see this being used by\nnontechnical people because they don't\nknow how to write specifications. They\nare also focusing on doing as less work\nas possible and keeping the human in the\nloop as minimal as possible. They just\nwant to let their AI run autonomously.\nAnd their prompts usually look something\nlike this. Build me a Facebook clone.\nBuild me a YouTube clone. Or build me a\nmilliondoll SAS. This is what I've been\nworking on instead. It's called agentic\ncoding. And in comparison to vibe\ncoding, you are the orchestrator. You\nare the architect. You are the one who\ndrives the decisions and specifications\nwith the goal of amplifying your skills,\nnot replacing them. For comparison, this\nis what a prompt might look like for a\nperson who is doing agentic coding.\nLet's say that I notice one service of\nmine in my codebase is being scattered\nand wiring is across five different\nfiles. I will create a prompt like this.\nCreate a plan to consolidate a service\nwhich is currently being maintained\nacross five different files. Use an\narchitectural style that matches our\ncurrent codebase. Keep the structure\nflat and do not introduce too many\nabstractions. Just by this prompt, you\ncan already understand that whoever is\ndoing this is on top of their codebase.\nThey aren't using AI to replace their\nskills or to think for them. They are\nsimply using it to speed up what they\nwould do anyway themselves. That brings\nus back to this ideal improved version\nof my tutorials where I don't rebuild\nthe project in front of you but record\nmyself building it for the first time. I\nsaid that this isn't possible because of\nhow long it would take. But with Agentic\nCoding, I can now reduce hundreds of\nhours of thinking and typing into just a\nfew hours of prompting. That is why I\ndecided to build a two-week workshop\nwith a new module dropping every few\ndays. In this workshop, you can\ndigestibly consume this content. And in\neach module, I show you how I approach\nimplementing a new feature rather than\ntelling you what is the next line of\ncode for the entire chapter. The\ndifference between learning through a\nworkshop in comparison to my YouTube\ntutorial is a night and day difference.\non YouTube. Everything works the first\ntry and you can just passively listen to\nme tell you the next line of code. In\nthis workshop, you're almost forced to\nactively observe my thoughts and my\nprompts. So, you can apply the same to\nyour codebase. Agentic coding, as better\nas it is from vibe coding, is still\nnon-deterministic, which means that more\nlikely than not, your version of this\nproject will be different than mine,\nwhich is exactly what we want. I don't\nwant you to clone what I do. I don't\nwant you to copy what I do. I want you\nto understand my technical decisions and\nthen recognize the same in your codebase\nand learn how to apply them. This is by\nfar the most valuable piece of content I\nhave created in the last 3 years. It is\nstill as easy to follow along as my\nYouTube tutorials, but it forces you to\nthink. It forces you to come up with\nyour own solutions and recognize bad\npatterns in your codebase the same way I\nrecognize them in my codebase. You end\nup with the skill to build anything\nrather than just one finished project\nlike you do in my YouTube tutorials. I\nwant to teach you how to code like\nAntonio, not how to code with Antonio. I\nfinally want to show you how I think and\nit will be exclusively available on\ncodewithantonio.com.\nThis workshop will start very soon and\nnow is the perfect time to grab your\nseat early with a massive 40% discount.\nGrabbing your seat early also means that\nyou have early access to the YouTube\nvideo source code live office hours with\nme in the discord where you can ask me\nany questions and you also get a proper\nlive cohort experience with a new module\ndropping as the curriculum has been\norganized. Once the cohort has started,\nyou will no longer be able to purchase\nthe live experience of it. So, make sure\nyou grab your seat now. This is the very\nfirst time that I'm providing such a\nunique learning experience and I\ncouldn't be more excited to finally\nannounce it and to finally go live with\nthe cohort. Go ahead and grab your seat\nearly. And lastly, I want to hear what\ndo you think about this new way of\nteaching? And if you would like to see\nme introduce some varying content on\nthis channel besides the 10-hour\ntutorials. For example, how about an\nhour of just refactoring and nothing\nelse? Or an hour of just fixing errors.\nI think that's a unique perspective and\na closer experience to the reality of\ncoding than my massive 10-hour\ntutorials. I want to start a new\ndirection of this channel where I still\nproduce high-quality tutorials but also\ngive you a lower barrier to entry so you\ncan actually get some value out of my\nvideos without having to invest 10, 20\nhours into it. Let me know what you\nthink and see you in the next",
  "transcript_chars": 8242,
  "ingested_at": "2026-05-12T01:11:38.843667+00:00",
  "source": "channel",
  "yt_meta": {
    "view_count": null,
    "like_count": null,
    "channel_id": null,
    "categories": null,
    "tags": null
  }
}