I'm 19 and I already burned out.
People told me I was too young to burn out. "You're a teenager, what do you even have to be tired about?" Turns out, your body doesn't check your birth certificate before shutting down.
I'm writing this because when I was in the middle of it, I looked for articles about burnout and found nothing that felt real. Just corporate wellness advice like "practice mindfulness" and "set boundaries." Cool, thanks, very helpful when you can't even open your laptop without feeling sick.
So here's my actual story. No sugarcoating.
How I got there
Here's what my schedule looked like for about six months.
University during the day. Lectures, labs, assignments. The usual student stuff. I study programming, so at least it's related to what I do. But it's still hours of sitting in classrooms, dealing with deadlines, doing group projects where you end up doing everything yourself.
After classes, I'd come home around 4-5 PM and switch to freelance mode. I'm an iOS developer. Swift, SwiftUI, the whole Apple ecosystem. Freelance clients don't care that you had a long day at uni. They have deadlines. So I'd work on client projects until 9 or 10 PM.
On weekends, I'd work on my own side projects. I had apps I wanted to build. I had ideas I was excited about. Well, "excited" is doing a lot of work there. More like "felt obligated to work on."
Then there was the content creation. I run a Telegram channel. I was writing articles for Dev.to. Making digital products for Boosty. Every night, after everything else, I'd squeeze in an hour or two of content.
Sleep? Four, maybe five hours on a good night. Coffee became less of a drink and more of a personality trait. I'd joke about it. "I run on coffee and deadlines." People thought it was funny. It wasn't funny.
I was doing all of this because I believed this was what success looked like. YouTube videos and Twitter threads showed people grinding 16 hours a day and loving it. The hustle culture content never showed the crash. So I thought something was wrong with me when I started not loving it.
I felt productive. I felt like a machine. I was outputting code, content, products, assignments. Everything was getting done. Until the machine broke.
The symptoms I ignored
It didn't happen overnight. Burnout is slow. It's like a phone battery that starts draining faster and faster until one day it dies at 40%.
The first sign was that code stopped being fun. I know how that sounds. "Boo hoo, coding isn't fun anymore." But if you're a developer, you know what I mean. That feeling when you solve a problem and it clicks. That little dopamine hit when your code compiles and works on the first try. Gone. Just gone.
Opening Xcode started feeling like opening a textbook for a subject you hate. I'd stare at the file navigator and feel nothing. Or worse, dread. The app I was building for a client, the one I'd been excited about two months ago, now felt like a prison sentence.
I started getting headaches. Not the "I need some water" kind. The kind that sits behind your eyes and doesn't leave for days. I blamed it on screen time. Bought blue light glasses. Didn't help.
My focus was shot. I could barely concentrate for 20 minutes before my brain would just wander off. I'd catch myself scrolling Twitter instead of writing code. Not even reading tweets. Just scrolling. My thumb moving on autopilot while my brain checked out completely.
I started hating my own projects. The side projects I'd started because I was passionate about them? They disgusted me. Every time I opened one of those repos, all I could see was more work. More things to fix. More features to add. An infinite todo list that I'd built for myself voluntarily.
I stopped replying to messages. Friends texting me? I'd see the notification, think "I'll reply later," and then not reply for days. Freelance clients asking for updates? I'd draft a response, delete it, and put it off. My Telegram channel? Silence.
Sunday nights became the worst. That specific dread of knowing tomorrow starts the cycle again. Lying in bed at 2 AM, too tired to sleep, too wired to rest, scrolling through my phone and dreading the alarm that's set for 7 AM.
I kept telling myself this was temporary. Just push through this semester. Just finish this client project. Just launch this product. There was always a "just" in front of something.
The breaking point
I remember the exact moment it hit me.
It was a Tuesday night, around 11 PM. I had a freelance deadline on Friday. The project was maybe 60% done. I opened Xcode, created a new SwiftUI view file, and typed struct. Then I stopped.
I sat there staring at that blinking cursor for almost an hour. I wasn't stuck on a technical problem. I wasn't planning my approach. My brain was just empty.
I couldn't write a single line of code.
My hands were on the keyboard. I knew what I needed to build. I'd done this a hundred times before. Simple stuff. A list view with some API data. Nothing complicated. But my brain refused to turn the knowledge into keystrokes.
I closed my laptop and sat in the dark. And then I did something I hadn't done in months. I actually asked myself: "Are you okay?"
The answer was very clearly no.
I missed that freelance deadline. First time ever. I sent the client some excuse about being sick. Technically true, I guess.
What actually helped
Recovery wasn't clean or linear. Some weeks were better. Some weeks I'd slip right back into the old patterns. But over a few months, these things made a real difference.
1. I took a full week off
I don't mean a "work from bed" week or an "I'll just check my emails" week. An actual, real week off.
No code. No content creation. No "productive" podcasts about startups and hustle culture. No checking GitHub notifications. I deleted Slack and Telegram from my phone for seven days.
I slept. A lot. I watched stupid YouTube videos that had nothing to do with programming. I went for walks without listening to anything. Just walked and looked at things.
It felt wrong. Every hour, my brain would scream that I was falling behind. I had to actively fight the urge to open my laptop and "just check one thing."
That week taught me something uncomfortable. The world kept spinning without my commits. Nobody died because I didn't post on my Telegram channel. The freelance clients survived.
2. I set hard boundaries
No laptop after 9 PM. Period. Not "unless there's a deadline." Not "just for 30 minutes." The laptop gets closed at 9 PM and doesn't open again until morning.
This was harder than it sounds. The first few nights I just sat in my room not knowing what to do with myself. I'd been filling every waking minute with screens and work for so long that I'd forgotten what people do in the evenings.
Turns out, people read books. Watch movies. Talk to their families. I'd forgotten that was an option.
3. I dropped two freelance clients
This was terrifying. Freelance income was a big part of my budget. Saying no to money when you're 19 and trying to build something feels insane.
But I looked at my workload honestly and realized I had the capacity for two clients, not four. I finished the current projects, then told two of them I wasn't available for new work. I was as professional about it as I could be.
My income dropped. But so did my anxiety. Turns out the trade-off was worth it.
4. I started sleeping 7-8 hours
Revolutionary, I know.
I'd been treating sleep like a luxury for so long that sleeping 8 hours felt lazy. I literally felt guilty the first few mornings when I woke up at 8 AM instead of 6 AM. "Successful people wake up at 5 AM," my brain would say. Cool. Successful people also don't have mental breakdowns over a SwiftUI view file.
The difference was immediate and embarrassing. Better focus. Fewer headaches. Code that I wrote actually made sense the next day instead of being a mess I'd have to rewrite. I was more productive in 6 focused hours than I'd been in 12 exhausted ones.
All those months of grinding on 4 hours of sleep, I thought I was being productive. I was actually just being present. Sitting in front of my laptop for 14 hours doesn't mean you're working for 14 hours. It means you're working for maybe 4 hours and staring at your screen in a daze for 10.
5. I stopped coding for fun (temporarily)
This one hurt the most. My side projects were my passion. They were the reason I got into programming. But they had become just another obligation on the pile.
So I stopped. For about a month, I only coded for university and for my remaining freelance clients. No personal projects. No "fun" apps. No experimenting with new frameworks on Sunday mornings.
After about three weeks, something weird happened. I saw a tweet about a new SwiftUI API and felt a tiny spark of "oh, that's cool, I want to try that." It was small. But it was the first time I'd actually wanted to code in months.
I didn't immediately rush to my laptop. I let that spark sit there for a while. When I eventually did open a personal project again, it was because I wanted to. Not because my schedule said I should.
What I do differently now
It's been a few months since the worst of it. I'm not going to pretend I'm "cured" or that I've got everything figured out. But some things changed permanently.
I sleep 7-8 hours now. I don't care what the deadline is. I don't care how close I am to finishing something. The bug will still be there in the morning, and I'll be better equipped to fix it after actual rest.
I stopped treating weekends as bonus workdays. Now I try to do at least one thing each weekend that has nothing to do with screens or code. Go somewhere. See someone. Anything that reminds me I'm a person and not a code-producing unit.
I'm learning to say no. Every opportunity looks amazing when you're young and hungry. New client? Yes. New project idea? Yes. But every yes is a no to something else. Usually sleep or the people around you. I'm getting better at turning down good opportunities so I can actually handle the ones I've already said yes to.
I stopped caring about my GitHub commit graph. I used to feel guilty on days when it was empty. No green square meant no progress. That's insane. Some of my best ideas came on days when I didn't write any code at all.
And I stopped thinking of rest as the opposite of work. You wouldn't drive a car for 10,000 miles without an oil change and then act surprised when the engine dies. Your brain is the same.
You're not a machine
If you're reading this and you recognize yourself in any of what I described, please stop. Close the laptop. Go outside. Drink some water instead of your fourth coffee.
The code will be there tomorrow. The clients will understand. The side project can wait another week.
You got into programming because you loved building things. If you keep going at a pace that kills that love, you'll end up with a career you hate and skills you resent. And the worst part is, you'll think it's normal because everyone around you is doing the same thing and pretending they're fine.
I'm not going to give you a motivational speech. Burnout sucks. Recovery is slow and boring and frustrating. Some days you'll feel great and some days you'll want to throw your MacBook out the window.
But you're 19. Or 22. Or 25. Or 40. Whatever age you are, you have time. You don't need to build everything right now. You don't need to prove anything to anyone at 2 AM on a Tuesday.
Take the break. I promise the code will still be there when you get back.
If you found this useful, I share more stuff like this on Telegram and sell developer toolkits on Boosty.
Top comments (0)