Most developers stop building massive side projects once they start working full time, but the ones who keep growing shift their focus from building products to solving specific curiosities. The exhaustion you feel after an eight hour day is not a lack of ambition. It is decision fatigue. You spend your entire workday making high stakes architectural choices and debugging complex logic, which leaves your brain with very little capacity to do the same thing for fun at 6 PM.
When you are a student or a bootcamp learner, coding is the primary activity of your day. Your brain is wired to seek the dopamine hit of a passing test or a working feature. Once you enter the workforce, the context changes. Coding becomes a series of meetings, Jira tickets, and pull request reviews. The "magic" of building something from scratch is replaced by the maintenance of a massive, existing codebase.
This shift creates a psychological gap. You remember the version of yourself that spent weekends building random apps, and you feel like you are losing that edge. This often leads to a guilt cycle. You tell yourself you should be building a side project to stay competitive, you open your IDE, you stare at the screen for twenty minutes, and then you close it because you are mentally drained. You then feel guilty for not being "productive," which makes the idea of coding feel like another chore rather than a hobby.
Decision fatigue is a real cognitive phenomenon. Every time you choose a variable name, decide between a map or a filter, or argue for a specific design pattern in a meeting, you consume a finite amount of mental energy. By the time you log off, your "decision tank" is empty.
Building a side project from scratch requires an immense amount of decision making. You have to choose the stack, the database, the hosting provider, and the feature set. This is why you find it easy to watch a movie or play a game (where the rules are set) but find it impossible to start a new React project. You are not lazy. Your brain is simply protecting itself from more cognitive load.
"I used to feel terrible that I couldn't spend 10 hours a week on my own apps after work. Once I realized I was just burnt out from my day job, I switched to small 30 minute learning bursts. It saved my sanity."
- Marcus, Senior Backend Engineer
The mistake most developers make is trying to maintain the same "student" workflow while holding a full time job. You cannot expect to put in 40 hours of professional work and then 20 hours of side project work without hitting a wall. Instead, you need to change the definition of a side project.
Stop trying to build a "startup" or a "complete app." These projects have too much overhead. Instead, focus on "micro-projects" that have a clear beginning and end. A micro-project is something you can finish in one or two sittings.
These small wins provide the dopamine you need without the crushing weight of a massive backlog. They allow you to feel the growth without the exhaustion of project management.
There is a difference between learning a new concept and building a project. Many devs think they must build a full app to "learn" a new language or framework. This is inefficient. If you want to learn how Rust handles memory, you don't need to build a full web server. You can read the documentation and practice the specific concepts.
This is where you can reduce the friction of staying sharp. Instead of fighting your way through a 500 page PDF or a massive documentation site every night, you can use StudyCards AI to convert those technical PDFs into flashcards. By exporting these to Anki, you can maintain your knowledge of new languages or system design patterns in 15 minutes a day using spaced repetition. This removes the need to open your IDE every single night just to feel like you are "growing."
If you want to avoid the feeling of being glued to a screen, move your planning phase away from the computer. One of the biggest hurdles to starting a side project is the "blank screen" effect. When you open your laptop, you are reminded of your work emails and Jira tickets.
Try using a physical notebook for your side project ideas. Spend 20 minutes on a Sunday afternoon sketching out the logic or the data flow of a small tool you want to build. When you actually sit down to code on a Tuesday night, you aren't making decisions. You are simply executing a plan you already wrote down. This bypasses the decision fatigue and makes the actual coding process feel like a puzzle rather than a chore.
It is also okay to simply stop coding after work for a while. The industry pushes a narrative of "constant hustle" and "permanent learning." This is a recipe for burnout. Some of the best engineers are those who have a complete disconnect between their professional and personal lives. They exercise, read fiction, or spend time with family, and they return to work on Monday with a refreshed brain.
If you find that you genuinely hate the idea of opening your laptop after 5 PM, listen to that feeling. You can still grow professionally by being more intentional during your 40 hours of work. Volunteer for the harder tickets, ask to lead a design review, or spend an hour of your work day reading the source code of the internal libraries your company uses.
If you still feel the need to keep your skills sharp but can't bring yourself to start a project, try these low-energy alternatives. These methods keep you in the loop without requiring you to enter a "deep work" state when you are already exhausted.
You don't need to build a second full time job in your spare time to be a great engineer. Focus on small wins and efficient learning systems that fit your energy levels.
No. While side projects can help juniors get their first job, senior engineers are judged on their professional impact. Solving a complex production bug or improving system latency at your job is more valuable than a half finished Todo app in your GitHub profile.
Stop relying on motivation and start reducing friction. Instead of "building an app," tell yourself you will spend 15 minutes on one specific task. Often, the hardest part is just opening the IDE. If you still feel drained, switch to passive learning like reading or using flashcards.
Focus on CLI tools, browser extensions, or small automation scripts. Anything that solves a personal problem and can be completed in a weekend is ideal. Avoid projects that require complex authentication, payment gateways, or massive database migrations.
Use a combination of official documentation, technical whitepapers, and spaced repetition. Tools like StudyCards AI can convert these documents into Anki cards, allowing you to memorize core concepts and syntax without the overhead of managing a full project codebase.
Generate Anki flashcards free