kokobob.com

A Developer's Journey: Lessons Learned About Value and Recognition

Written on

Chapter 1: The Beginning of My Developer Career

In my initial role as a developer, I was determined to make a mark. Although my salary was quite low, I understood that this was my first opportunity in the field. The company had never employed a developer and was hesitant about the decision. My main task was to "transition the product from their existing POS software to an online platform."

Software Developers: The Overlooked Heroes

Despite the dedication you put into your work, the likelihood of receiving recognition is often minimal.

Developer at work on a computer

The software operated on AS/400 systems, characterized by a stark black interface with bright text and lacking mouse functionality.

AS/400 system interface

While there was a method to export data, the quality was poor. The product descriptions lacked consistency, making it challenging to import into the new website. As I collected additional requirements, the team kept suggesting features they wished to have. After spending two weeks cleaning the data, I dedicated several months to developing their desired online application.

Initially, the website was meant to function as a catalog, allowing customers to log in and browse products. It soon evolved into a comprehensive e-commerce platform, complete with live inventory for ordering and an API for customer integration—all while they continued to use their outdated POS system. As a sole developer, I invested an inordinate amount of time into the project, balancing front-end development, graphic design, back-end work, and data entry. I often found myself working an extra 4 to 6 hours after my regular shift.

After two years and with the application generating substantial revenue, my boss invited me out for lunch. It was an unusual occurrence, as he rarely took anyone out other than his partners. We went to a burger restaurant, and I was surprised to be sharing drinks with my boss.

During our meal, he expressed deep gratitude for my contributions. Just the week prior, he had reviewed the company's year-end results and was astonished by the growth—from $12 million to $18 million in sales. He attributed this success solely to my hiring. “After discussions with the sales team, they noted an influx of positive feedback about the website and its impact on their sales,” he said.

As he elaborated on my role in the company’s achievements, I couldn't help but anticipate a significant bonus. However, as the meal concluded, the waiter presented two checks without any further comments from my boss. A few moments later, as I reached for my credit card, he insisted, “No worries, I’ll cover this.” We then returned to the office, and I was left in disbelief. I thought surely there would be some form of recognition for my efforts.

The following day, I struggled to focus at work, anxious about what my boss might reveal. A few hours later, he approached me with a smile and asked, “How did you enjoy that burger yesterday? It was delicious, right?” I responded affirmatively, but that was the last I heard from him that day.

Feeling disheartened, I couldn't reconcile the idea that my boss would take me out to lunch, praise my contributions, and not offer any financial reward. My hopes rested on payday, believing it would bring the recognition I felt I had earned.

When payday arrived, I sat at my desk, eagerly awaiting my paycheck. My boss entered with a familiar phrase, “Thanks for all you do,” as he handed me my check. Excited, I opened the envelope, only to find the same amount I had always received. A few moments later, he casually remarked, “That burger was fantastic. We should go back sometime.”

Throughout the week, he repeatedly referenced that lunch, and while my work ethic remained unchanged, my enthusiasm waned. I stopped putting in extra hours and ceased proposing new ideas, even as the company continued to thrive.

Years later, as I moved on to different opportunities, that experience remained etched in my memory. The lesson? Never accept a free lunch, as it may come with strings attached. And yes, here’s your burger.

Reflecting on career lessons

Dino Cajic is currently the Head of IT at LSBio (LifeSpan BioSciences, Inc.), Absolute Antibody, Kerafast, Everest BioTech, Nordic MUbio, and Exalpha. He also holds the position of CEO at MyAutoSystem. With over a decade of experience in software engineering, he possesses a B.S. in Computer Science and a minor in Biology. His expertise encompasses the development of enterprise-level e-commerce applications, research-based software projects, and knowledge dissemination through writing.

Connect with him on LinkedIn, follow him on Instagram, or subscribe to his blog and Medium publication. Explore more stories from Dino Cajic and thousands of other writers on Medium. Your membership directly supports writers and grants you access to all stories on the platform.

Chapter 2: Valuable Insights from Fellow Developers

The first video titled "5 Signs of an Inexperienced Self-Taught Developer (and how to fix)" discusses common pitfalls faced by self-taught developers and offers practical solutions for improvement.

The second video "The most undervalued part of Kanban - Pawel Brodzinski" sheds light on overlooked aspects of the Kanban methodology, emphasizing its importance for efficient workflow management.

Share the page:

Twitter Facebook Reddit LinkIn

-----------------------

Recent Post:

Escape the Procrastination Cycle: Embrace Your Inner Wolves

Discover how to break free from procrastination by understanding your inner struggles and using mindfulness techniques.

Understanding the Emotional Landscape of Dating an Abuse Survivor

Insights on supporting a partner who has survived abuse, emphasizing the importance of unconditional love.

The Influential Thinkers Who Shaped My Learning Perspective

An exploration of key thinkers who have influenced my philosophy of learning and skill acquisition.