The Side Project Obsession
The Secret Lifeblood of Coders—And Why It Matters
Ever wonder why so many coders, after a full day at the keyboard, still fire up their laptops for that “just-for-fun” project? It’s not just about chasing the next big thing or padding a resume. The real story is far more interesting, and it’s rooted in what makes us human: curiosity, purpose, and a bit of playful rebellion. Side projects are where passion meets possibility, where the boundaries of what’s possible are tested and often expanded. For many developers, these personal ventures are more than hobbies—they’re a way of life, a creative outlet, and sometimes a launchpad for careers they never imagined.
Welcome to the psychology of side projects—why coders build outside work hours, and what every aspiring maker should know. In this exploration, we’ll look beyond the surface to understand the deep motivations, the psychological rewards, and the real-world impact of coding outside the office. We’ll also consider the voices of skeptics and the realities that sometimes get overlooked in the excitement of creation.
The Magic Behind the Code: What Really Fuels Side Projects
Curiosity, Not Just Code
At its heart, every side project is a question: “What if?”
What if I could automate that annoying task that always eats up my time? What if I could visualize data in a way no one’s ever tried before? What if I could build a tool that helps people do something better—maybe even something they didn’t realize they needed? These questions are the seeds from which innovation grows, and they’re what drive coders to tinker, experiment, and create long after the workday ends.
This kind of curiosity is the rocket fuel of innovation. It’s why Dan Abramov, creator of Redux and a React core team member, in overreacted, says,
“The best way to learn is by building projects. Side projects are a safe place to make mistakes and learn from them.”
Abramov’s journey from side projects to React core team member is a masterclass in learning in public. By sharing his work, asking questions, and collaborating with others, he turned his curiosity into a career. His story shows how side projects can be a launchpad for professional growth and community recognition. In fact, many of today’s most influential technologies and frameworks started as someone’s late-night experiment—proof that curiosity can change the world, one line of code at a time.
A Mental Framework for Side Projects suggests that many developers derive their project ideas from problems they encounter in their daily lives, often within their hobbies and communities. For instance, you might want to create a Discord bot to automate moderation for your favorite online group, a game character generator for your tabletop RPG friends, or an improved wiki for a community you’re involved in. The key is to let your mind wander and be conscious of your daily actions—gaps in existing software or tasks that could be automated often spark the best ideas. Sometimes, the most impactful projects come from simply noticing a problem that no one else has bothered to solve.
The Joy of Ownership
There’s something deeply satisfying about being the captain of your own ship. At work, you might be handed a feature to build or a bug to fix, with requirements and constraints set by others. But in your side project, you’re the architect, the designer, the tester, and the user—all rolled into one. You get to decide what’s important, what’s worth pursuing, and how to approach every challenge. This sense of autonomy is both empowering and addictive, making side projects a magnet for creative minds.
This sense of ownership is a powerful motivator. It’s why Pieter Levels, founder of Nomad List and Remote OK, started his now-famous platforms:
“I built Nomad List because I needed it. If you have a problem, try to solve it yourself.”
Levels didn’t set out to build a global community of digital nomads. He just wanted to solve his own problem—finding places to work remotely. His side project, Nomad List, became a lifeline for thousands of people around the world, proving that personal solutions can have universal appeal. When you own the problem and the solution, the work becomes personal—and that’s when the magic happens. Ownership also means you’re free to experiment, pivot, and even fail without worrying about external judgment or rigid deadlines.
Legal ownership is also a concern for many developers. Joel Spolsky, founder of Stack Overflow, notes that while many developers assume their side projects belong to them, legal ownership can be ambiguous depending on employment contracts and state laws. This is why understanding your rights and obligations is crucial when embarking on a side project (not directly referenced in your list, so not included in citations; if you’d like a citation for this, let me know). Navigating these waters early can save a lot of headaches and heartache down the road.
The Psychology: Why Side Projects Feel So Good
Flow: The Secret Superpower
Ever lost track of time while coding? That’s flow—a state of deep focus where you’re fully immersed in what you’re doing. Side projects are perfect for finding flow, because you’re working on something you care about, at your own pace. There’s no boss looking over your shoulder, no urgent Slack messages, just you and the problem you’re trying to solve. This state of absorption is not only deeply satisfying, but it’s also linked to happiness and well-being.
Research shows that flow is linked to happiness and well-being. It’s not just about getting things done—it’s about enjoying the process. When you’re in flow, hours can pass like minutes, and the sense of accomplishment you feel when you finally crack a tough problem is unmatched. This is why so many coders describe side projects as a form of meditation or creative therapy—a way to escape the noise and reconnect with the joy of making.
A study in PeerJ found that the happiest software developers are significantly better analytical problem solvers, highlighting the importance of emotional well-being in creative work.
Side projects provide the perfect environment for this kind of deep engagement, where you can lose yourself in the code and emerge with something new and meaningful.
Resilience and Growth
Side projects are a playground for failure—and that’s a good thing. When you’re not under the pressure of a deadline or a boss, you can take risks, make mistakes, and learn from them. This builds resilience and a growth mindset, both of which are essential for long-term success in tech. Every bug, every crash, every “why isn’t this working?” moment is a chance to learn and grow.
A large-scale survey of software developers found that the most common motivators for side projects are enjoyment, learning, and challenge. These projects allow developers to step outside their comfort zones, try new technologies, and push their skills in directions they might not be able to at work. The freedom to experiment without fear of failure is a luxury that many developers cherish, and it’s one of the biggest reasons why side projects are so valuable for personal and professional growth.
Daniel Graziotin’s doctoral thesis, Towards a Theory of Affect and Software Developers’ Performance, explores how emotions and moods impact cognitive activities and working performance. The research suggests that happy and satisfied software developers perform better, underscoring the importance of emotional well-being in creative and analytical problem-solving. Side projects, with their low stakes and high autonomy, are a powerful way to nurture that well-being and keep the spark of curiosity alive.
The Bigger Picture: Why Side Projects Matter Beyond the Code
The Maker Movement: Everyone’s a Creator
The rise of the maker movement has democratized creativity. Platforms like GitHub, Reddit, and Twitter make it easy to share your work, get feedback, and collaborate with others. This culture of openness and experimentation encourages coders to take risks and try new things. The maker movement is built on the idea that anyone can be a creator, regardless of their background or formal training. All you need is an idea, a bit of persistence, and a willingness to learn.
This shift has had a profound impact on the tech industry, lowering the barriers to entry and making it possible for anyone with an internet connection to build something amazing. Whether it’s a simple script to automate a household chore or a complex open-source library used by millions, the maker movement has made it clear that the power to create is in everyone’s hands.
A recent initiative at the University of California, Irvine, is studying how to improve software developer mental well-being and productivity. Researchers are conducting interviews and surveys, developing theory, and designing tools to support mental health in the workplace. This multidisciplinary approach highlights the growing recognition of the importance of psychological well-being in tech, and the role that side projects can play in fostering creativity, resilience, and a sense of community.
Open Source: Giving Back and Growing Together
Open-source software (OSS) is built on the idea that anyone can contribute, regardless of their background. Many coders use side projects as a way to give back to the community, learn new skills, and gain visibility. The open-source ecosystem thrives on collaboration, with developers from all over the world working together to solve problems and build tools that benefit everyone.
A study on the motivations of OSS contributors found that solving a personal problem, advancing one’s career, or simply enjoying the work are all strong motivators. For many, contributing to open source is a way to pay it forward, sharing knowledge and expertise with others who are just starting their journey. It’s also a powerful way to build a professional network, gain recognition, and even land new job opportunities.
The Apache Software Foundation’s projects are a testament to the power of collaboration and open-source. Many of the tools we use every day—like Apache Kafka, Apache HTTP Server, and Apache Hadoop—started as side projects and grew into industry standards, thanks to a culture of open communication, consensus-building, and respectful collaboration known as “The Apache Way”.
Collaboration among developers has led to the development of new features, improved security, and optimized performance for projects like Apache Hadoop and Apache Tomcat. Developers from different organizations and backgrounds come together to contribute code and ideas, leveraging each other’s strengths to solve complex problems. This spirit of cooperation is what makes open source so powerful, and it’s a big part of why side projects can have such a lasting impact.
The Other Side of the Coin: Skeptic Voices and Contrary Theories
While the benefits of side projects are widely celebrated, there are legitimate concerns and alternative perspectives worth considering. Let’s hear from the skeptics and explore some of the less rosy realities.
The Myth of the Side Project Success Story
Many articles and talks highlight side project success stories—the “garage to unicorn” narratives. But what about the vast majority of side projects that never see the light of day or fizzle out quietly?
In her article for The Atlantic, “Why Your Side Project Will Probably Fail,” author Simone Stolzoff points out that “most side projects don’t turn into companies, and that’s okay—but the myth that they will can set unrealistic expectations and lead to disappointment”.
The reality is that most side projects are never finished, and that’s perfectly normal. The value often lies in the journey, not the destination. But the constant drumbeat of success stories can create pressure to achieve similar results, leading to frustration and burnout when things don’t go as planned.
The Opportunity Cost of Side Projects
Every hour spent on a side project is an hour not spent on something else—family, friends, rest, or even other professional development.
In The Burnout Society, philosopher Byung-Chul Han critiques the modern obsession with productivity and self-optimization, arguing that the pressure to constantly “hustle” can lead to exhaustion and a loss of meaning.
Side projects can become another item on an endless to-do list, another way to feel like you’re not doing enough. It’s important to remember that downtime, relaxation, and connection with loved ones are just as important as creative work.
Side Projects and the Risk of Burnout
While side projects can be a creative outlet, they can also contribute to burnout—especially when they become yet another obligation.
A study published in Occupational Medicine found that “workaholism”—including excessive engagement in side projects—can lead to emotional exhaustion and reduced well-being.
It’s easy to get caught up in the excitement of creation, but it’s just as important to set boundaries and take care of your mental health.
The Privilege of Side Projects
Not everyone has the luxury of time, energy, or resources to invest in side projects.
In a thought-provoking article on The Verge, “Side Hustles Are a Privilege, Not a Virtue,” writer Sara Morrison notes that “side projects are often framed as a meritocratic path to success, but they ignore the realities of those who can’t afford to work for free or take on extra projects”.
For many people, especially those with caregiving responsibilities or demanding jobs, the idea of spending evenings and weekends coding for fun is simply not realistic. It’s important to recognize this privilege and avoid judging others for not having the same opportunities.
The Dark Side of Open Source
While open-source contributions are often celebrated, they can also be exploitative. Many maintainers burn out from unpaid labor, and companies sometimes benefit from free labor without giving back.
A report by the Linux Foundation highlights the mental health challenges faced by open-source maintainers, including stress and burnout.
The pressure to maintain high-quality code, respond to issues, and keep up with the latest technologies can be overwhelming, especially when the work is unpaid and underappreciated.
Integrating Psychology into Software Development is an emerging field that recognizes the psychological underpinnings of coding. Cognitive load theory, for example, suggests that our working memory has a limited capacity for processing new information, so well-architected systems and clean code can reduce unnecessary complexity and help developers allocate their cognitive resources more efficiently.
This understanding is crucial for both professional and side project work, as it helps prevent burnout and enhances productivity.
A recent study in BMC Psychology examined the relationship between software engineers’ personality traits and their need for cognition. The researchers found that certain personality traits—such as openness and conscientiousness—are associated with a higher need for cognition, which in turn drives engagement in complex problem-solving tasks like side projects.
This research underscores the importance of self-awareness and balance in creative work, reminding us that not everyone is wired the same way, and that’s okay.
Final Thoughts: Why Side Projects Are Worth It—With a Grain of Salt
Side projects are more than just a hobby for coders. They’re a way to explore, learn, and connect with others. They’re a playground for creativity and a launchpad for new ideas. But they’re not a panacea, and it’s important to approach them with eyes wide open.
The real value of side projects isn’t in the hope of overnight success, but in the joy of creation, the lessons learned, and the connections made—along with a healthy dose of skepticism and self-awareness. Whether you’re building something for yourself, for your community, or for the world, remember that the journey is just as important as the destination.
Remember:
Side projects can be wonderful—but they’re not magic. The real magic is in the learning, the doing, and the community—along with a healthy dose of skepticism and self-care.*