Dear Dev, What Are You Coming Back To?
I've been noticing more conversations lately about burnout, losing motivation, and starting over in tech. It's not just about being tired. Sometimes people still want to code. They still want to build things. They still want to be part of technology. But somehow, they don't know how to get back to it, or even what they are trying to get back to. And I think that's an important distinction. The…
Recent discussions are highlighting burnout, loss of motivation, and the desire to start anew within the tech industry. It's not solely about feeling exhausted; many individuals still have a passion for coding, creating, and contributing to technology. However, they often struggle to reengage or determine their intentions. This distinction is crucial.
Traditional burnout advice typically includes taking a break, exercising, and maintaining a healthy lifestyle. These measures can offer immediate relief, but they may not always address the underlying sense of restlessness. Resting doesn't always alleviate that unsettling feeling. One might feel disengaged even after taking time away.
Perhaps the issue isn't always about adopting a new productivity strategy or taking another break. Sometimes, individuals need to reconnect with their initial reasons for being in tech. The speaker discusses their own experience with consistency and how it became insufficient. While their One Commit a Day project encouraged daily contributions, they realized that merely having a daily goal or a list of tasks wasn't enough.
They felt the urge to ponder their purpose and aspirations. As a result, they added journaling and reflection to One Commit a Day v2. The project continues to emphasize consistency by encouraging daily actions, but it now also prompts self-reflection to understand the underlying motivations. The concept of "TO-BE" was introduced, drawing inspiration from Japanese journaling methods that focus on personal growth rather than just task completion.
For the speaker, "TO-DO" pertains to what needs to be done daily, while "TO-BE" focuses on the direction and values they want to embody as a technical individual. Unlike a five-year career plan, TO-BE is an ongoing process of self-discovery, allowing individuals to pause and evaluate what truly matters to them, especially when their circumstances evolve.
The speaker acknowledges that they don't have all the answers, but they aim to provide a space for reflection alongside their daily commitment. One Commit a Day v2 now includes journals dedicated to technical pursuits, AI, and technology, with the ultimate goal being to help individuals step back and contemplate their personal journey.
The author expresses that they don't have definitive answers but hopes that others will find value in the project and engage in the ongoing conversation about their own paths.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
