Technologies!
Old tech is expensive. Hard to hire for. Hard to maintain. Hard to understand. Overengineering is just as bad. Don’t reinvent the wheel. Always evaluate total cost, building and owning the solution.
Where Tech Companies Lose Money?
Sometimes it’s obvious. Sometimes it’s invisible — until it’s too late. Let’s break down the most common places where tech companies of any size bleed revenue
Incidents!
Every incident costs money and reputation. Firefighting isn’t enough. You need postmortems, root causes, prevention. Throwing more infrastructure at incidents doesn’t scale forever. Sooner or later, you hit the ceiling.
Working in IT - choose technology that solve core needs, not ones that just look good on a CV. Poor knowledge of 5 databases is worse than deep expertise in 2.
If your company has 50+ people, it's time to document your processes.
Start small.
Make them clear, effective, and flexible.
Think of it as a one-time investment that pays off every quarter.
Stop ignoring processes in IT!
They’re costing you more than you think — in time, money, and team sanity.
What feels like “agility” at first often turns into chaos as you scale.
When employees aren’t sure what to do, they self-align.
Sounds good?
It’s not.
It leads to:
– Wasted time
– Anxiety
– Miscommunication
– Redundant work
– Lost money
Forget job titles in IT. There is no standard.
A Team Lead at one company can look like a Tech Lead at another.
Stop worrying about titles—focus on responsibilities.
Engineers love tech experiments. Businesses avoid them. But not every “modern” tool is worth the risk. 99.99% won’t survive. The real skill is knowing when to innovate and when to stick with what works.
The most dangerous hire - A careless manager!
Skills or passion can carry you far but when someone doesn’t care at all, especially in leadership, it spreads.
One disengaged manager can demotivate hundreds of people.
If they won’t improve, let them go.
Culture dies in silence!
Bridging business & tech isn’t easy. Stakeholders want speed. Engineers want stability.
Here's how we balance both:
- Speak business, not just tech
- Be honest about expertise
- Know your system
- Innovate wisely. Simple > clever. Most problems are already solved
The Peter Principle is real!
People get promoted until they’re no longer good at their jobs.
I avoid this by checking two things before promoting:
- Do they have the skills for new role (or potential)?
- Do they want it?
Otherwise, no one wins.
Working more ≠ working better.
Burnout leads to mistakes, not results.
Your job isn’t to be a hero — it’s to deliver reliably.
Unknowns happen, but managing expectations is part of the job.
You were hired for your skills — and one of those is knowing when to ask for help.
You don’t need unit tests!
At least if your mistakes cost more which applicable to big tech companies only.
Good integration tests + UI tests can be enough. Unit tests are fragile, costly, and often duplicate coverage.
Think about ROI — not coverage %.