14/08/2026
๐๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ ๐ข๐ฌ ๐ง๐จ๐ญ ๐ญ๐ก๐ ๐ฌ๐ญ๐ซ๐๐ญ๐๐ ๐ฒ. ๐๐ญ ๐ข๐ฌ ๐ญ๐ก๐ ๐ฅ๐๐ฏ๐๐ซ.
One thing Iโve learned as a Software Developer is this:
A business does not need ๐ฆ๐จ๐ซ๐ ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ just because technology is available.
It needs the ๐ซ๐ข๐ ๐ก๐ญ ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ ๐๐จ๐ซ ๐ญ๐ก๐ ๐ซ๐ข๐ ๐ก๐ญ ๐๐ฎ๐ฌ๐ข๐ง๐๐ฌ๐ฌ ๐ฉ๐ซ๐จ๐๐ฅ๐๐ฆ.
Because you can spend millions on software and still have:
โ slow processes
โ disconnected systems
โ poor customer experiences
โ data nobody uses
โ teams doing manually what should have been automated
โ expensive systems that solve the wrong problem.
Thatโs why I donโt look at technology as simply โ๐ฃ๐ถ๐ช๐ญ๐ฅ๐ช๐ฏ๐จ ๐ข ๐ธ๐ฆ๐ฃ๐ด๐ช๐ต๐ฆ, ๐ด๐ฐ๐ง๐ต๐ธ๐ข๐ณ๐ฆ ๐ฐ๐ณ ๐ข๐ฏ ๐ข๐ฑ๐ฑโ
I look at the ๐๐ฎ๐ฌ๐ข๐ง๐๐ฌ๐ฌ ๐๐๐ก๐ข๐ง๐ ๐ญ๐ก๐ ๐ฌ๐ฒ๐ฌ๐ญ๐๐ฆ.
What are we trying to achieve?
Where is the bottleneck?
What should be automated?
What data should decision-makers actually see?
How should the systems communicate?
What needs to scale?
And most importantly, ๐ฐ๐ข๐ฅ๐ฅ ๐ญ๐ก๐ข๐ฌ ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ ๐๐ซ๐๐๐ญ๐ ๐ฆ๐๐๐ฌ๐ฎ๐ซ๐๐๐ฅ๐ ๐๐ฎ๐ฌ๐ข๐ง๐๐ฌ๐ฌ ๐ฏ๐๐ฅ๐ฎ๐?
Because good technology should not just ๐ฅ๐จ๐จ๐ค ๐ข๐ฆ๐ฉ๐ซ๐๐ฌ๐ฌ๐ข๐ฏ๐.
๐๐ญ ๐ฌ๐ก๐จ๐ฎ๐ฅ๐ ๐ฆ๐๐ค๐ ๐ญ๐ก๐ ๐๐ฎ๐ฌ๐ข๐ง๐๐ฌ๐ฌ ๐๐๐ญ๐ญ๐๐ซ.
For business owners and decision-makers, the question isn't:
"๐๐จ ๐ฐ๐ ๐ง๐๐๐ ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ?"
The better question is:
"๐๐ก๐๐ญ ๐๐๐ง ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ ๐ก๐๐ฅ๐ฉ ๐ฎ๐ฌ ๐๐จ ๐๐๐ญ๐ญ๐๐ซ, ๐๐๐ฌ๐ญ๐๐ซ, ๐ฌ๐ฆ๐๐ซ๐ญ๐๐ซ ๐๐ง๐ ๐ฆ๐จ๐ซ๐ ๐ฉ๐ซ๐จ๐๐ข๐ญ๐๐๐ฅ๐ฒ?"
That is where my interest in technology gets really exciting.
I donโt just want to write code.
๐ ๐ฐ๐๐ง๐ญ ๐ญ๐จ ๐ฎ๐ง๐๐๐ซ๐ฌ๐ญ๐๐ง๐ ๐ญ๐ก๐ ๐ฉ๐ซ๐จ๐๐ฅ๐๐ฆ, ๐๐๐ฌ๐ข๐ ๐ง ๐ญ๐ก๐ ๐ฌ๐จ๐ฅ๐ฎ๐ญ๐ข๐จ๐ง, ๐๐ง๐ ๐๐ฎ๐ข๐ฅ๐ ๐ญ๐๐๐ก๐ง๐จ๐ฅ๐จ๐ ๐ฒ ๐ญ๐ก๐๐ญ ๐ฆ๐๐ค๐๐ฌ ๐๐ฎ๐ฌ๐ข๐ง๐๐ฌ๐ฌ ๐ฌ๐๐ง๐ฌ๐.
And honestly, that conversation is far more interesting than just talking about code.
