My Journey as a Developer Without Passion

I'm a senior web developer working at a startup in Houston, and I want to share something that sets me apart from many developers I've come across.

Contrary to the common narrative, web development isn't my passion. In almost every interview I attend or conduct, there's a strong emphasis on the importance of 'passion.' Whether it's about the team being 'passionate' about the product or the Lead Developer exhibiting 'passion' for coding, this word is omnipresent in the tech world. I may have used it myself in the past, perhaps even believed it then, but the truth is, it doesn't resonate with me.

Having said that, I understand if I've just distinguished myself from the majority of startups that thrive on underpaying developers while promising a chance to indulge in their 'passion' using the 'latest and greatest technology.' Now, let me clarify why web development became my profession. I suspect there are many developers out there who, like me, do not find their motivation aligning with the idealized version the media and employers often present.

In my younger years, I dabbled in programming and web development without much progress. It wasn't until my teenage years that I ventured into freelancing. My motivation was straightforward: there was demand for it, I had the skills, and it brought in some modest earnings, mostly in the form of a few haircuts, chiropractic adjustments, and numerous disappointments.

The turning point in my programming journey, beyond basic HTML and CSS, occurred when I reconnected with my close friend, Raphael Caixeta, after several years of not talking. Raphael was a successful web developer, featured on Mashable early in his career and proficient in selling web properties at a profit. He was the right business-minded individual with the right skills at the right time. Coincidentally, it was the right time for me too.

At that point, I was juggling a 30+ hour per week job at a department store while attending college. Although my monthly income was decent for a 19-year-old, it paled in comparison to what Raphael was making. The moment that changed everything for me occurred one night when I was celebrating my meager paycheck with a cheap cigar and browsing the web.

Raphael messaged me, stressed but excited about a challenging client project. The client wanted a custom WordPress blog with a completely different back-end. Raphael despised the WordPress dashboard but appreciated its functionality. With just nine hours overnight, he had to create an entirely new back-end on top of WordPress. Despite his efforts to convince the client to settle for a WP dashboard redesign, the client insisted on a complete overhaul, and he was willing to pay for it.

I laughed at Raphael's predicament, thinking how fortunate I was to enjoy a good night's sleep while he toiled away coding for a demanding client. Little did I know, the next morning, Raphael sent me a screenshot of his PayPal account, displaying an amount that was one and a half times my monthly earnings. I had spent 30 hours every week at a department store, and what Raphael accomplished overnight, took me 45 days.

It was a wake-up call.

Raphael had urged me multiple times to pick up web development again, reminding me of my interest in it when I was younger. Finally, this incident pushed me over the edge, and I delved back into learning.

A few months later, I was restarting my freelancing career.

The bottom line: I got into it for the money.

money…ain’t it funny?

Throughout my career, my primary motivation has always been money. Not the allure of cutting-edge technology, not a burning passion for a specific field, not the desire to make a significant impact or create groundbreaking products – just money (and benefits, of course; benefits were a major factor). When I embarked on my first full-time job, it wasn't because I was enthusiastic about it. Quite the opposite, in fact – the idea of working in an office filled me with dread. But I had my reasons, rooted in a certain level of greed. I craved financial stability, the allure of a steady income, and, most importantly, the opportunity to move out of my apartment and into a house with my best friend, who is now my wife.

The initial months were challenging. My best friend and I had lived together for over a year, and adjusting to spending eight hours apart every day was tough. I had previously chosen contract work to avoid the soul-draining monotony associated with office jobs. However, the financial incentives and benefits made the situation more bearable. Suddenly, we could afford new clothes, buy regular groceries, and even provide our dogs with high-quality food instead of relying on discounted scraps.

With time, we grew to appreciate this improved lifestyle. We could dine at restaurants, indulge in hobbies that were once financially out of reach (like going to the gym or playing video games), and enjoy our spacious rental house. All of this positive change came from one job offer – we went from having very little to having everything we needed.

Subsequent career moves were guided by the need to secure employment and increase my income. I rapidly escalated my earnings, doubling my initial salary within a couple of years of my first full-time position. At one point, I even tripled it (although I eventually opted for a role with superior benefits, albeit lower pay).

The allure of better benefits became a significant factor in my job choices. I transitioned from meager time off to guaranteed paid time off, from lacking health insurance to enjoying comprehensive coverage, and from rigid office requirements to a fully remote work environment.

When evaluating job opportunities, the deciding factor for me was always money and benefits. It wasn't about the specific technologies being used, the presence of perks like "beer in the fridge," or even the allure of company equity (which always carries some degree of risk). A job that allowed me to work from the comfort of my home held far more appeal than any technical stack or innovative software setup could ever offer.

But I do enjoy it

I do find programming enjoyable, no doubt about it. If I didn't, I wouldn't have reached the level I'm at. However, it's not my passion; it's my hobby. A hobby that happens to be incredibly lucrative, treats me well, and affords me the freedom to pursue what truly ignites my passion.

A few years back, my wife questioned why I complained about work when it was something I enjoyed. She couldn't understand why I didn't seek a job aligned with my true passion. Explaining my reluctance was challenging, but one thought prevailed: people shouldn't turn their passions into work.

There's a saying, which I'll paraphrase, suggesting that your job shouldn't be your passion. Converting your passion into work can strip away the enjoyment. Instead, you keep your hobbies separate and engage in work that you can sustain long-term, something you find satisfying.

For me, programming fits this mold. It's a skill I excel at and enjoy, and it affords me the opportunity to explore various interests on the side.

My philosophy is simple: find work you can excel at and sustain over the long run. If it also allows you to pursue your passions outside of work, even better. That's the motto I live by.

What I enjoy about it

I find development incredibly enjoyable because it's akin to solving an intriguing puzzle. It's like playing with word Legos, except there are always new pieces to discover and incorporate into your projects. I have a genuine passion for learning, and my curiosity knows no bounds. Whether it's delving into the intricacies of Wikipedia for days, absorbing seemingly useless information, or immersing myself in the ever-expanding universe of technology, I revel in the process.

Technology is a lot like exploring an endless rabbit hole. The more you learn, the deeper it goes. You can never truly master it because it's constantly evolving, akin to the lore of a fictional universe where everything is in perpetual motion. The rapid pace at which things change ensures there's always something new to explore, even in the most current developments.

I find immense joy in this constant evolution. Every day, I can delve into numerous articles and absorb knowledge that I can apply to my projects the very next day. The dynamic nature of programming means you never get bored; as you acquire more knowledge, it becomes easier to pick up new skills.

There's an undeniable allure in this continuous learning process, a sense of excitement in adapting to the ever-shifting landscape of technology.

what am I passionate about?

Writing holds the top spot as my ultimate passion in life. Since the second grade, I've been crafting short stories, comics, novellas, novels, non-fiction books, blogs, and much more. Apart from working, writing consumes most of my time.

It's not my passion for development; it's my love for writing. However, the writing industry isn't financially rewarding, and the available writing jobs don't inspire me. The idea of ghostwriting for someone uninterested in the content or copywriting for magazines I don't care about doesn't appeal to me. The trade-off between writing and development doesn't favor me; development provides better opportunities.

That said, I wouldn't rule out a change if a fantastic opportunity arose. If one of my self-published books made it to Amazon's top 100 list and a publisher reached out, I might consider it. If I stumbled upon an incredibly compelling story that could be turned into an interactive book experience, I'd turn to Kickstarter for funding. And if luck smiled upon me like it did for E.L. James, I wouldn't hesitate to leave the development industry entirely. I'd continue coding, but programming, for me, is more of a hobby than a profession. I could easily switch to any of my other hobbies—music production, concept design, marketing, gaming, photography, and more—if they offered similar benefits. Who knows, maybe I will.

Passion differs from a hobby. Passion implies a desire for grandeur, progression, and self-satisfaction from efforts. A hobby, on the other hand, is a pastime for relaxation or simply something to do during leisure time.

Beyond writing, my greatest love is my child. I cherish spending time with her. Unlike some friends who can't due to their demanding jobs and long commutes, I am present for my daughter. I have the privilege of sharing breakfast, lunch, and coffee breaks with her. Moreover, I witness her incredible moments, like her first open-mouthed smile, which my wife often informs me about. I can't fathom being a teacher or working with other kids, but caring for my own child? That's my true passion.

Passion isn’t everything

You might wonder, who would want a developer without a burning passion for development? Well, I'd argue, most companies. I believe developers without an obsessive passion for coding can often be more effective than those who live and breathe code. A developer without overwhelming passion focuses on the task at hand, aiming to achieve the work goal, rather than being driven by an internal need for fulfillment.

Of course, who's to say for sure? Based on my past experiences, my employers have generally been content with my work, and that's my only measure.

I am employed where I am not because I have an insatiable urge to code, which I enjoy, but because I want the startup to thrive. I genuinely appreciate our product. The code itself holds little personal significance for me. It's a tool that serves its purpose, gets the job done efficiently, is rigorously tested to avoid disrupting existing functionality, and follows a streamlined workflow. These elements are means to an end, helping me minimize wasted time and focus more on accomplishing my tasks. While writing the code was enjoyable, it's merely a method to achieve my goals, nothing more.