DEV Community

Cover image for I Finished 47 Tutorials and Built Nothing
AheadKit
AheadKit

Posted on

I Finished 47 Tutorials and Built Nothing

9:04 AM. Saturday. The plan, written on a sticky note and stuck to the monitor so I could not pretend I never made it: BUILD SOMETHING TODAY. One thing. Anything. The folder is already there, on the desktop, called my-app. Inside it: one file. A readme that says "TODO" and nothing else. I wrote that readme three weeks ago. It has aged well.

Coffee first. Then I open the laptop, and the first thing I do, the very first thing, is open a tutorial. Just one, I tell myself. To warm up.

9:31 AM. "Build a Complete App in 3 Hours (2026)." The instructor has a ring light and the confidence of a man who has never once been stuck. He says, "By the end of this video, you'll have a working app." I believe him. I always believe him. That is the first mistake, and I make it every time.

10:15 AM. Forty minutes in. The app is a to-do list. Of course it is. The instructor says, "Now the fun part," and opens a settings file with forty lines in it. I pause the video to look up one of the settings. The explanation I find mentions three more things I do not know. I open a tab for each of them. One tab is a definition that uses the word in its own definition. One is a forum thread from 2021 where two people argue about it for forty comments and nobody wins. The third is a video, twenty minutes long, and I watch four minutes of it before I remember the first video is still paused. The video is still paused. The video will stay paused for a long time.

11:02 AM. Tutorial one, abandoned at 68%. I tell myself I got the important parts. I did not get the important parts. The important parts were in the last third, where he connects everything together, which is the part I never reach. I open tutorial two: "The ONLY Guide You Need (2026 Edition)." The title alone should have told me. The ONLY guide. There have been six ONLY guides this year.

12:40 PM. Lunch. Tutorial two is at 71% and the instructor is building another to-do list. Another one. I need you to understand this: I have now watched four different people build to-do lists. I could build a to-do list in my sleep. I have never built a to-do list. The folder on the desktop still has one file in it. I eat standing up, watching the video, telling myself this counts as working. It does not count as working. I know it does not count as working. I keep watching.

2:18 PM. Tutorial three. This one promises "no fluff, just building." It opens with eleven minutes of the instructor explaining his setup. I watch all eleven minutes. Then he says, "First, let's install everything," and I follow along, and something fails, and the error message is in red, and I spend twenty minutes fixing an install problem for a project I do not have. When it finally works, I feel accomplished. I have accomplished nothing. The folder on the desktop still has one file in it.

3:47 PM. I do something I have never done. I count.

I open my learning account, the one with the certificates, and I count the finished courses. Forty-seven. Forty-seven completions. I scroll through them: the complete guide, the bootcamp, the masterclass, the crash course, the zero-to-hero, the ultimate guide, the definitive guide. The oldest one is from two years ago. "Introduction to Everything." I finished it on a Sunday and remember nothing except the instructor's mug, which said WORLD'S OKAYEST DEVELOPER. I have a certificate PDF in my downloads for a course I finished in March, and I cannot remember a single thing it taught me. I open the certificate. It has my name on it, spelled right, and a gold seal that is a picture of a gold seal. Forty-seven. I look at the number for a long time. Then I look at the folder on the desktop. One file. A readme that says TODO.

5:05 PM. Tutorial four. I open it the way you open the fridge when you are not hungry, not because you need it, because it is there and your hands need something to do. The title is "You Don't Need Another Tutorial." I watch it to the end. All twenty-three minutes. I do not see the problem with this until much later.

6:30 PM. Dinner. I eat at the desk, phone in one hand. A video starts playing: "Stop Watching Tutorials and Start Building." I watch it to the end too. The man in the video is very convincing. He says the first project should be small and ugly. He says done is better than perfect. I nod along, the way you nod along to advice you have no intention of taking. The video ends and another one starts on its own, because they always do. "Why You Can't Focus Anymore." I watch half of it before I notice what I am doing. Then I open tutorial five.

7:58 PM. Tutorial five is forty minutes long. I watch nine minutes of it, and then something happens that has never happened before. I get bored. Not the restless kind of bored, the kind that sends you looking for the next video. The finished kind. The kind where you look at the screen and think: I have seen this. I have seen all of this. The instructor is building a to-do list. I close the tab.

Then I do something else I have never done. I open the bookmarks folder — the one called LEARN, sixty-three links, every "watch later" I ever saved — and I delete it. The whole folder. Sixty-three links: a fourteen-hour video called "Learn Everything," a playlist called "watch before you build," one course I saved three times under three different names. It asks me if I am sure. I am sure. Sixty-three links, gone in one click. My hand is shaking a little. I tell myself it is the coffee. It is not the coffee.

9:40 PM. I open the folder on the desktop. The readme still says TODO. I delete the readme, and I write one file. One page. No framework, no install, no setup video. Six meals I actually make. Pasta, lentil soup, fried rice, eggs and toast, chicken curry, noodles. Not meals I wish I made, meals I make. And one button. You press the button, it picks your dinner. The button is grey because I did not look up how to colour it. Looking it up would have been another tutorial. The meals are in a list at the top of the file, the button picks one at random, and that is the whole program. Thirty-one lines. I count them twice, because I want the number to be real. The page has no styling at all. It looks like something from 1998. It took twenty-six minutes. It works. I sit and look at it for a while. It is the first thing in that folder that does something.

11:47 PM. I press the button. It says pasta. I go to the kitchen and make pasta. The page is ugly. The button is grey. The pasta is good.


P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam

Buy me a coffee

AheadKit on Gumroad — Beginner-Friendly Books & Packs

Top comments (0)