Balancing Enterprise Engineering with Personal Projects

Building a skyscraper is a complex endeavor, requiring meticulous planning, permits, and a large team. In contrast, constructing a backyard shed is a spontaneous, personal project that can be completed over a weekend. My career as an engineer has mirrored these two modes: by day, I work on large-scale banking systems, and by night, I tinker with personal projects in my 'shed.' While enterprise work has taught me the importance of scale and structure, it's the personal projects that have kept my passion for engineering alive.

In large-scale projects, much of the work isn't coding but involves design documents, test plans, and architecture reviews. These processes are crucial for handling the massive transaction volumes of a bank, teaching me defensive design and failure mode anticipation. However, this environment can be rigid, limiting experimentation.

My personal projects, on the other hand, allow me to apply the structural discipline learned at work in a space where I have complete freedom. Initially chaotic, these projects have evolved as I naturally integrated work patterns, leading to more robust and enjoyable creations. This freedom to experiment is invaluable, as it enables rapid learning and iteration without the high stakes of enterprise work.

Personal projects are where curiosity thrives. They offer a break from the repetitive nature of enterprise tasks and provide a playground for exploring new tools and concepts. This hands-on experience often translates back to my professional work, allowing me to make informed decisions rather than guesses.

The trap in software engineering is viewing your day job as the entirety of your craft. Without personal projects, creativity can stagnate, leading to burnout. Protecting these projects is crucial as they nurture curiosity, experimentation, and personal growth, ensuring that I remain passionate about building software.