Effort is a cost, not a result

Two engineers got the same problem on the same Monday: a monthly report that took far too long to load.

The first one went all in. Late nights, a weekend, a full rewrite of how the report pulled its data. By Friday he looked exhausted, and the new version was a little faster.

The second one spent his first hour asking the finance team what they actually used. The answer: three numbers, out of forty columns. He built a small page with just those three. It loaded instantly. He went home on time.

At the next team meeting, everyone praised the first engineer. "What a week. Real dedication."

Nobody mentioned the second one.

We clap for the wrong thing

Effort is easy to see. Late messages, long hours, a tired face in the morning. It looks like commitment, so we reward it.

Results are quieter. Sometimes the best result looks like almost nothing happened at all.

But effort is not the thing we deliver. It's what we pay to deliver it. Hours, energy, sleep, time with family. Every one of those is a cost. And a good team, like a good business, tries to get more done for less cost, not the other way around.

If the needle didn't move, the effort didn't count. That sounds harsh, but it's actually freeing. You don't have to prove anything by suffering.

Leverage beats labor

The engineers I admire most are not the ones who work the longest. They're the ones who look for leverage first:

• Ask before you build. One good question can save a week of work.
• Use the tools you have. AI, a ready-made service, a teammate who has solved it before.
• Aim at the finish line. Shipping is how you find out whether an idea works. Polishing in the dark isn't.

AI makes this even more important. A lot of the hard labor can now be done in minutes. If we still measure ourselves by hours spent, we're measuring the wrong thing.

Be proud of the outcome

None of this means effort is bad. Hard work matters when it's aimed at the right problem. Some problems really do need a long week.

Just don't confuse the two. Ask "what changed?" before you ask "how hard did we work?"

And the next time someone solves a big problem in a small amount of time, make some noise about it.

That's the work worth celebrating.