← ademola.dev / writing 4 min read
share →
reflectioncareermindset

The Illusion of Working Hard

Being busy and being productive are not the same thing. It took a toxic environment for me to finally understand the difference. · Sat, Jun 20, 2026

A few months ago, I joined a new company. What surprised me wasn’t the amount of code I was writing — it was how exhausted I felt despite writing less code than I had in previous roles.

My days became filled with meetings, explaining issues to QA, chasing code reviews, responding to messages, and constantly putting out fires. I was always busy, always occupied, always under pressure. From the outside, it looked like I was working harder than ever.

But was I really?

The more time I spent in that environment, the more I realized that being busy and being productive are not the same thing.

Every bug became a blame game. Some issues were inherited from previous engineers, others slipped through because of gaps in testing, and some were simply difficult problems that nobody immediately understood. Yet every incident seemed to require explanations, defenses, and finger-pointing.

The constant scrutiny was draining.

At one point, my manager called me a liar and a bad engineer because I couldn’t immediately identify the cause of an issue. That moment stayed with me. Not because I believed it was true, but because it planted doubt.

I began to question my abilities. I started wondering whether I was good enough. Every mistake felt larger than it was. Every bug felt like evidence that I didn’t belong.

The strange thing was that I wasn’t becoming a worse engineer.

I was simply spending more energy surviving the environment than actually doing the work.


Stress has a way of disguising itself as productivity. When you’re constantly anxious, constantly context-switching, constantly defending yourself, it feels like you’re working incredibly hard. Your mind is exhausted at the end of the day, so naturally you assume you’ve been productive.

But exhaustion is not always evidence of meaningful work.

Sometimes it’s evidence of unnecessary friction.

Looking back, I realized that the most productive periods of my career were not the ones where I felt the busiest. They were the periods where I had clarity, trust, focus, and enough psychological safety to solve difficult problems without fear.

A healthy environment allows engineers to think.
An unhealthy environment forces engineers to survive.

For months, I mistook stress for growth and busyness for productivity. In reality, I wasn’t moving forward. I was spending so much energy navigating the environment that I had little left for learning, building, or improving my craft.


The biggest lesson I learned is that hard work is not measured by how stressed you are, how many meetings you attend, or how exhausted you feel at the end of the day.

Real work creates value.

Everything else is often just the illusion of working hard.

Eventually, I decided to stop participating in it.

I stopped measuring my value by how stressed I felt at the end of the day. I stopped confusing constant urgency with meaningful progress. Most importantly, I stopped allowing my environment to define my growth.

Instead, I returned to learning outside of work.

I started reading again, building projects again, writing again, and exploring technologies that genuinely interested me. Not because I hated my job, but because I realized something important: I would never become the engineer I wanted to be if I relied solely on an environment that wasn’t helping me grow.

I still needed the job. Like most people, I had responsibilities and bills to pay. But I also understood that my career belonged to me.

No manager, company, meeting, or performance review could take away my responsibility to keep learning.

The moment I separated my job from my growth, everything changed.

I stopped seeing myself as a struggling engineer and started seeing myself as an engineer going through a difficult season. I realized that growth doesn’t always happen inside the workplace. Sometimes it happens in the quiet hours after work, when nobody is watching — when you’re learning because you’re curious, not because you’re being evaluated.

My job was a source of income. My growth was my responsibility.

And once I understood the difference, I stopped chasing the appearance of hard work and started investing in becoming better.

thoughts on this?

Hit reply — I read every email.

hello@demola.dev →
← Previous Getting Started with Jetpack Compose: A Flutter Developer's Perspective Next → The Hidden Cost of AI in Software Engineering