Shorter, more frequent technical writing — published directly, no editorial cycle.
Featured on cloud migration challenges in financial services — how legacy systems accumulate technical debt that makes cloud moves genuinely risky, and what it actually takes to move them without data loss or downtime.
Read on TechBullion →Featured on mentorship in software technology — the case for experienced practitioners teaching from lived production experience rather than theory, and what that looks like in practice across 75+ engineers mentored.
Read on IBTimes →On what the payment platform migration actually required beyond "move it to the cloud" — sequencing, risk, and the decisions that determine whether a migration succeeds or just relocates the problem.
Read on TechBullion →Technical articles covering enterprise architecture, event-driven systems, cloud-native patterns, and applied AI — submitted to peer-reviewed and practitioner publications.
On building a safety gate for ISO 20022 payment files — why the fix for unhelpful validation errors is a separate AI explanation layer, not a smarter error message, and why that layer must never touch the pass/fail decision itself.
Read on TDWI →On the step most teams skip when building LLM-assisted tooling — verifying that what the model says is actually true — and what a structured eval harness catches that manual spot-checking misses.
Read on VentureBeat →On the difference between technical debt (internal to implementation) and architecture risk (structural, determines what a system is capable of) — and why conflating the two gets both mismanaged.
Read on SD Times →On why most governance failures are decided long before a single line of code is written — and what actually has to change earlier in the process to fix it.
Read on Architecture & Governance →On the Kafka pipeline rebuild — what actually broke, why the fix wasn't just a config change, and the risk lessons that generalized well beyond that one system.
Read on NY Weekly →On why AI's biggest value in engineering isn't code generation, but cross-referencing documentation against real system behavior and ranking debugging hypotheses on codebases you didn't build.
Read on Built In →Publishers occasionally ask practitioners to technically vet manuscripts before publication — checking that the code, architecture, and real-world claims hold up.
Master eBPF and Cilium for unmatched cloud security, performance, and observability in modern cloud environments. Published on Amazon Kindle.
View on Amazon →Master DevOps pipelines, GitOps, DevSecOps, infrastructure as code, multi-cloud deployment, and AI-driven delivery automation. Published on Amazon Kindle.
View on Amazon →