02
Whichever layer
needs owning
I didn't set out to become the person who gets called when a database is on fire.
That happened by accumulation. First it was a PL/SQL pipeline on legacy Oracle
infrastructure that nobody else wanted to touch. Then a six-service monitoring
backend. Then a Kubernetes cluster running a platform that a national ministry
depends on staying up. Then an AI pipeline, because by that point owning "the layer
nobody else wants" had become the job description. Each one taught me the layer below
it wasn't optional to understand.
Since May 2024 I've been at IICT, BUET, embedded on government-scale assignments
where downtime isn't a metric, it's an incident. I started as Assistant Programmer
and was promoted to Programmer for the same reason I keep getting handed the harder
systems: I make the architectural call — ClickHouse for time-series throughput, Go
over the JVM to kill GC-jitter, RAG over fine-tuning because the documents are
dynamic — and I take it through to production myself.
I'm not on here looking for a job — I already have one. This site exists because
there's no good way to hand someone my actual technical range in a single link. If
you need something built or fixed — backend, frontend, infrastructure, AI, a database
that needs saving — email me and tell me what it is.
ruhan.9mri@gmail.com →
Cryptography & Applied Security
AI / LLM Systems Engineering
Distributed Systems
Linux Internals
Database Engineering