Be the asset, not the expense

Dalibor Jovic Author

⬇(PDF worksheet at the bottom)⬇

Some developers work hard for years and still get treated like a cost.

Not because they are bad.

Not because they are lazy.

But because the business does not experience their growth as business value.

That is the painful part.

You can know every system, help everyone, fix production issues, stay loyal, and still be seen as a necessary expense on a budget sheet. Useful, but not important enough to develop. Needed, but not exciting enough to invest in.

I learned this the slow way.

I worked in a corporate internet provider where IT felt like something the company had to pay for, not something it wanted to grow. We had stable jobs, known systems, familiar people, and enough work to keep everyone busy.

But for years, there was no real money for conferences, courses, specializations, or pay increases.

At one point, I asked if we could get money for courses.

A top boss answered in front of around 40 people: “Our experience is that when we send people to specialization, they leave afterwards.”

That sentence explains a lot.

To him, learning was not an investment. It was a risk.

One colleague later said the sentence I wish I had been quick enough to say myself: “But what if we do NOT send people on specialization, and they stay?”

Exactly.

What happens if people stop learning, stop growing, and stay comfortable for years?

You do not get loyalty. You get stagnation with an employee badge.

And if you are the developer inside that system, you slowly start believing that this is normal. No conferences. No courses. No new tools. No pay movement. Just work, delivery, tickets, and “maybe next year.”

Here’s the uncomfortable part: a stable job can still make your career weaker.

It can feel safe while quietly removing the weight from the training bar.

You know the systems. You know the people. You know who to ask. You know how the meetings go. You are tired, but not challenged. Busy, but not growing.

That is when you need to ask the real question:

Does this company see me as someone worth growing, or as a cost to maintain?

The sentence that changed how I saw my career

Around that time, we had consultants helping us. And one thing was strange to me.

None of them wanted permanent positions in our company.

This made no sense in my head. We were a 300-person company. Stable. Secure. Benefits. Predictable. Very adult, if you will.

One consultant worked in a company with around 20 other consultants, and I casually told him he should ask for a job with us.

He laughed, then he said: “I am the biggest asset in my company.”

That sentence stayed with me.

Because I immediately understood what he meant.

In the internet provider company, I was one of the expenses.

In his consultant company, he was the investment.

His company sent him to conferences, courses, and specializations. They wanted him to become better, because every new skill made him more valuable to clients, projects, and the business.

My company did not want to buy me a new mouse when the old one died.

That contrast was hard to ignore.

Same industry. Same type of work.

Completely different view of the person doing it.

Expense companies ask: “How do we keep this cost under control?”

Asset companies ask: “How do we make this person more valuable?”

And this is where many developers get stuck.

They think career growth means doing good technical work inside one stable job and waiting for someone to notice.

Sometimes that works.

But often, nobody notices, because you are solving problems inside a system that has already categorized you as maintenance cost.

You are keeping the train running, but nobody sees you as the person who can drive it somewhere better.

That consultant made me realize something I did not want to admit:

I did not only need more skill.

I needed to become harder to ignore.

Being an asset is not a job title

Being an asset is not about having “senior,” “lead,” “principal,” or “architect” in your title.

I have seen people with strong titles create chaos.

I have also seen people without impressive titles become the person everyone trusts when things are difficult.

Being an asset is how the business experiences you.

Do you solve problems without creating five new ones?

Do you communicate early, before the surprise becomes expensive?

Do you understand why the feature matters, not only how to build it?

Do you prepare before meetings? Do you think through objections, owners, deadlines, next steps, and backup plans?

This is where I learned a lot from working with consultants from companies like McKinsey, Capgemini, and similar.

At first, I thought they were just smarter.

Then I noticed something annoying. Many were not better engineers.

But everything around them moved more smoothly.

They came prepared. They had written things down. They knew why the meeting existed. They knew what had been discussed before. They knew what decision they wanted. They knew who needed to be involved. They had a plan B.

The visible part was confidence. The invisible part was preparation.

That is professionalism.

Not the fancy suit version. The useful version.

Professionalism is mostly invisible discipline.

It is doing the thinking before other people have to ask for it.

Technical skill gets you into the room.

Communication, preparation, business understanding, and trust keep you there.

And in the AI era, this matters even more.

If code becomes cheaper to produce, the value moves to judgment, framing, verification, communication, risk control, and knowing what good looks like. The developer who only waits for tickets becomes easier to replace. The developer who understands the problem behind the ticket becomes more valuable.

That is the shift.

Start packaging your value

If you want to become an asset, do not start with a speech.

Start with evidence.

Keep a bragging document.

Every month, write down one big thing you did.

Not 40 small tasks. One meaningful thing.

A production issue you solved. A process you improved. A difficult feature you delivered. A risk you reduced. A decision you helped clarify. A teammate you helped unblock. A customer problem you made smaller.

Write it down while you still remember it.

Because six months later, when you sit in a growth conversation, your brain will betray you. You will remember that you were busy, tired, and useful, but you will not remember the details.

And details are what make value visible.

A bragging document is not ego.

It is your career memory.

It helps you see patterns. It helps your manager understand your impact. It helps you prepare for salary talks, role changes, interviews, and performance reviews.

It also forces an uncomfortable question:

Did I do anything this month that mattered?

If the answer is no, good. Now you know.

You can fix what you can see.

Choose environments that invest in growth

You also need to look honestly at your environment.

Some companies will not invest in you no matter how good you become.

They may like you. They may need you. They may even panic if you leave.

But they still see development as a cost, not as fuel.

That does not automatically mean you should quit tomorrow. I am obviously not a rocket surgeon, and I do not know your mortgage, family, market, or situation.

But you should stop pretending the signal is not there.

If a company never sends people to conferences, never pays for learning, never gives new challenges, never rewards ownership, and treats every growth request as a threat, you have information.

Use it.

Either become visibly more valuable where you are, or start moving toward a place where growth creates business value.

That could be consulting. It could be leadership.

It could be AI.

It could be architecture, product thinking, security, communication, teaching, or strategy.

The exact path matters less than the direction.

Stop sitting as a passenger in a company that only maintains you.

Start building the skills, reputation, and proof that make you worth investing in.

Be so good they cannot ignore you.

And then make sure they can actually see it.