I Took a Break. Here's What I Learned About Burnout as a Student Developer.

I disappeared for three weeks.

No posts. No commits. No "learning in public" tweets. Just silence.

If you've been following my journey, you know I've been grinding hard—building AI pipelines on a phone, writing due diligence reports, trading forex, hunting for internships, and carrying 7 courses at UNIZIK. I was shipping every week. Until I wasn't.

This post isn't a tutorial. It's what I learned from hitting a wall and actually stepping back.

The Warning Signs I Ignored

I didn't wake up one day and decide to stop. It crept in. First, I stopped replying to messages as fast. Then I started doom scrolling instead of coding. Then a whole week went by and I hadn't opened Termux or written a single line.

I told myself I was just tired. I'd bounce back tomorrow. Tomorrow turned into three weeks.

Looking back, the signs were there:

· I'd open my code editor and feel nothing. No excitement. No curiosity. Just blank.
· I was working on 7 different things—Substack, Dev.to, forex, cold outreach, internship apps, school, AI projects—and none of them were getting my full attention.
· I started comparing myself to every other developer I saw online. A guy in my department earns $2,700/month from a US company. Instead of motivating me, it made me feel behind.

What the Break Actually Taught Me

The guilt was the worst part. Every day I didn't post, I felt like I was losing momentum. Like I was letting myself down. Like three weeks of silence would undo months of work.

But here's what I realized: the work was still there when I came back.

My Substack posts were still live. My Dev.to articles were still getting reads. The Gemma 4 challenge entry was still competing. My portfolio didn't vanish because I took a break. It waited for me.

What I'm Doing Differently Now

I'm not coming back to the same grind. I'm coming back with rules:

1. One platform per day. Not all three. Monday is Substack. Wednesday is Dev.to. Friday is X. The others get rest.
2. No more 7-way multitasking. I pick two priorities max per week. This week: Substack comeback post + one Wellfound application. That's it.
3. Rest is part of the schedule, not a punishment. I used to feel guilty for watching a movie or playing a game. Now I know those moments are what keep the engine from exploding.
4. Comparison is a compass, not a weapon. That guy earning $2,700? He's proof the path exists. He's not proof that I'm failing. There's a difference.

What I'm Building Next

I'm revisiting my local AI pipeline—the RAG system I built on my phone using Gemma 4. Google dropped an update while I was gone, and the new model variants fix some of the exact pain points I hit in my original build. Smaller footprint. Better context handling. Apache 2.0 license.

I'll be documenting the rebuild. Not as a perfect tutorial. As a real, messy, "let me figure this out" series.

If You're in the Dip Right Now

You're not lazy. You're not falling behind. You're just human, and humans need rest.

The code will still be there. The portfolio will still be there. The opportunities will still be there. Take the break before the break takes you.

See you in the next post. 🚀