We help businesses connect cloud foundations, automation, and AI-assisted workflows into systems built for clarity and scale.
Joined June 2025
- Tweets 163
- Following 11
- Followers 7
- Likes 0
127 Photos and videos
Pinned Tweet
May 27
Most infrastructure does not disappear cleanly.
It stays somewhere: in old commits, unused environments, forgotten dashboards, DNS records no one revisits, and systems everyone assumes someone else still owns.
The dangerous part is rarely the thing itself. It is the moment the team stops remembering it exists.
The full breakdown: tardi.tech/2026/05/21/hidden…
7
Jun 11
Some placement decisions expire without the workload changing.
The service still runs. The bill looks normal. Nothing breaks.
But data residency, customer geography, or audit expectations may have moved around it.
Performance is not the only question.
#CloudCompliance #DataResidency #TardiTech
Jun 8
The workload evolved.
Traffic grew. Usage shifted. Data moved.
But the placement decision stayed where it was.
That is how cloud cost drift often starts: not with a bad call, but with an outdated one.
1
3
Jun 4
A cloud placement decision does not fail all at once.
It expires quietly while pricing shifts, new options appear, and the workload itself changes.
The original call was right. The question is whether it still is.
May 29
Every cloud cost meeting eventually produces at least one sentence that sounds like a hostage negotiation.
“It’s temporary.”
“We’ll clean it up later.”
“Do we still need that environment?”
“Who created this?”
Infrastructure has an excellent memory.
#FinOps #CloudCost #Engineering #DevOps
1
5
May 26
More visibility tools do not create recognition.
Recognition comes from structure: ownership, tagging, decision logs, and a standing question about why a workload is where it is.
2
May 24
Dashboards are a snapshot. Bills are a memory. When they disagree, the dashboard is usually wrong about the layer.
1
4
May 22
Anyone who has not lived this is welcome to comment. We will assume your week has been gentler than ours.
Have a peaceful and calm weekend! 🤘
2
3
23
May 20
Your attack surface is what you launched, plus what you forgot to retire.
Mostly the second one.
1
1
3
25
May 20
Web Security Auditor helps surface infrastructure that quietly remained exposed over time: security-auditor.tardi.servi…
1
5
May 18
Many breaches start with credentials that sat in commit history long enough to be forgotten.
3
8
May 14
Most security risks are the boring stuff that stopped being checked. Old credentials. Forgotten endpoints.
Permissions nobody removed because nobody knew who added them.
2
3
8
May 13
Trusted packages can still create untrusted consequences.
Socket reported 84 compromised TanStack npm package artifacts as part of the ongoing Mini Shai-Hulud supply-chain campaign.
Some were tied to millions of weekly downloads.
What gets installed is part of your attack surface.
#SupplyChainSecurity #DevSecOps
ALT Trusted packages. Untrusted consequences. A compromised dependency can put your code, your secrets, and your pipeline at risk.
1
3
90
May 13
The most expensive line in a cloud bill is rarely the loudest one.
Usually, it is the service nobody revisited because it kept working.
3
10
May 7
Cloud bills rarely change overnight. The drift starts in places nobody is checking. Five things hiding in the bill you already have.
3
9
Apr 30
Most teams start with optimisation. Reduce usage, improve efficiency, control cost.
Over time, that explains less. Systems can be well-tuned and still expensive. Constraints show up without obvious inefficiencies.
At that point, it’s not optimisation.
It’s architecture.
2
7
Apr 28
Most teams think in binaries.
Cloud or on-prem. Managed or self-hosted. Full control or none.
Reality is messier.
Control is layered. Infrastructure, runtime, data, access, operations don’t move together.
Systems drift. Costs stay high.
Not inefficiency. Distribution.
You don’t control everything. You decide what matters.
#CloudArchitecture #FinOps #PlatformEngineering
2
4
Apr 21
Most systems aren’t placed deliberately.
They start somewhere and stay there.
The system evolves.
The environment doesn’t.
That’s when constraints show up.
Not inefficiency. Misfit.
This isn’t optimisation.
It’s placement.
And placement isn’t fixed.
#CloudArchitecture #PlatformEngineering #CloudOps
3
6