AI
2 storiesApplied machine learning, agentic systems, evaluation, and LLM production pipelines.
|
🇬🇧Search published writing across AI, software engineering, product platforms, engineering leadership, and strategy, or browse directly by topic desk.
29 published stories across 9 desks
Applied machine learning, agentic systems, evaluation, and LLM production pipelines.
Engineering growth, interviews, technical writing, and career compounding over time.
Latest: What I Did at the CTO Level — Business Strategy Through Technology
Backend architecture, Go, databases, distributed systems, and performance debugging.
Latest: Integer to Roman: The Greedy Mapping That Always Shows Up in InterviewsFaith
Personal reflections on faith, discipline, clarity, and everyday grounding.
View Faith desk
Engineering management, organizational design, hiring, and pragmatic technical judgment.
Latest: The Ultimate Framework for High-Signal Technical Leadership
Essays on tools, personal workflows, reading notes, and cross-disciplinary observations.
Latest: World Cup 2026: The Biggest, Most Controversial Tournament Ever
Product discovery, marketplace platforms, fintech rails, and building reliable user workflows.
Latest: I Built a Cyber Insurance Platform for Australia's Largest Insurer from Indonesia — Here's the Full Architecture
Postmortems, yearly reviews, architectural trade-offs, and honest lessons from shipping software.
Latest: The $55K/Year Tech Debt Nobody Noticed — How I SOLD a Massive Refactor to Management (And WON)
Platform strategy, platform economics, build-vs-buy decisions, and long-term technical leverage.
Latest: The CTO Demands a Rewrite. The CEO Demands ROI. Here is the Ultimate Framework to Bridge the GapBreaking down the integer to Roman numeral conversion problem — from basic Roman numeral rules, the subtractive notation pitfalls (IV, IX, XL...), to a clean, interview-ready greedy O(1) solution. Complete with mapping table, step-by-step visualization, and why this approach is optimal given the 1-3999 constraint.
Master the classic coding interview problem 'Best Time to Buy and Sell Stock' with step-by-step explanation — from the naive brute force approach, recognizing patterns, to the optimal one-pass O(n) solution using sliding window / two-pointer technique. Complete with array visualization, complexity analysis, and the intuition behind every decision.
48 teams, 16 host cities across 3 countries, 104 matches, and an estimated $11 billion price tag. The 2026 FIFA World Cup is breaking every record — including the ones nobody wanted broken. From human rights scandals to environmental catastrophe, here's the full story behind the glitter.
At this level, your portfolio isn't about technology — it's about how technology created business value. I reduced AI inference costs by 90%, built an MCP orchestration that 3x'd developer output, and established a FOSS strategy where every repo is a 24/7 portfolio asset. This is what engineering leadership actually delivers.
No production experience. GitHub full of tutorial repos. One asset: the ability to learn fast and zero fear of breaking things. This is what I actually built as a junior engineer — WordPress sites, a PHP university system, and the hardcoded credentials mistake that taught me security forever.
I shipped real features to real users. I broke production and fixed it alone at 2 AM. I built a mobile banking app with 680K downloads, a mining fleet system saving $200K/year, and a field operations platform for 4.1M users. This is what mid-level engineering actually looks like — the projects, the metrics, and the production incidents that made me a real engineer.
I stopped being evaluated on lines of code. I was evaluated on decisions — what architecture to use, what trade-offs to accept, and how to guide other developers. This is the real story of designing IoT telemetry for 50K events/sec, microservices for Australia's largest insurer, and the stack decision that became my most-read article.
A staff engineer doesn't just solve hard problems. They solve problems that prevent other engineers from being productive. I built a multi-tenant LMS framework serving 100+ universities, a dynamic form engine adopted by 3 teams, and an ISO 8583 bridge that became the org standard. This is what staff-level leverage actually looks like.
Your portfolio should reflect your seniority level, not just list every project you've touched. Junior engineers sell potential and fundamentals. Senior engineers sell depth and architecture. Staff engineers sell leverage. CTOs sell business outcomes. Here's exactly what to put in your portfolio at each level — with concrete examples and a universal format you can use today.
A candid career retrospective tracing my journey through every engineering role: Junior developer grinding through fundamentals, Mid-level shipping production features, Senior designing architectures, Staff building org-wide leverage, and CTO-level strategic decisions. Each section maps to the portfolio strategy framework with real projects, real metrics, and real lessons.
A comprehensive list of professional services I've delivered across multiple industries: IoT fleet management, fintech core banking integration, cyber insurance platforms, education technology, and enterprise digital transformation. Each service backed by real production systems still running today.
From the first user query to the response stored in the database. A complete guide to layers, tools, request flow, learning roadmap, and real-world production implementation — including the newly released Google ADK.
Most developers think accessibility is 'not urgent' until they get sued. Learn WCAG 2.2, POUR principles, and implementation techniques you can apply immediately before your digital presence becomes a legal nightmare — and more importantly — a human failure.
OpenSpec is good for 'architectural blueprints'. But BMad goes further — with specialized agents, 4 end-to-end phases, and an intelligent guide that makes AI coding feel like a real engineering team.
MiniMax M2.7 isn't trendy to talk about. But check its benchmarks — it beats GPT-4o, Claude, and Gemini in almost every category. And the price? 10x cheaper. Why is nobody talking about it?
Some founders proudly build products from scratch using Ollama on a Rp 50 million PC. We break down why that's delusion, not innovation — and why a Rp 320k/month subscription is far more sensible.
N+1 is just the tip of the iceberg. Beneath it lie Cartesian Explosion, Lost Update, God Table, Replication Lag, ORM Trap, and 15 other far more dangerous problems — complete with real-world case studies and Golang solutions.
Vibe Coding is like asking a contractor to build a house without a blueprint — the result? Chaos by the third month. OpenSpec arrives as an 'architectural blueprint' for AI coding, shifting the paradigm from random chatting to structured Spec-Driven Development.
Model Context Protocol (MCP) is an open standard connecting LLMs with external data and tools — like USB-C for AI. Learn the architecture, how it works, and my real-world setup: 11 MCP servers from MySQL, Firebase, Grafana LGTM, to Lighthouse.
Stop drowning in noise and start leading with extreme clarity. Discover the 'High Signal-to-Noise' framework that separates elite technical leaders from those who just attend endless meetings. Learn how to slay Conway's Conway's Law, build psychological safety, and scale your engineering impact without burning out.
A head-to-head benchmark of 7 popular programming languages: performance, memory, concurrency, developer experience, and the hiring market. Discover exactly why Go dominates production at millions of requests — and why I almost jumped ship to Rust (but didn't).
From Jakarta to Sydney: how I built Cybera360, a platform combining automated risk assessment, real-time vulnerability scanning, and cyber insurance quoting — protecting 10,000+ SMEs across Asia Pacific.
Your MVP was built in record time, but now every new feature takes 3X longer? This is the raw, unfiltered true story of how silent tech debt secretly devoured $55,000/year — and the EXACT framework I used to convince management that refactoring is an explosive investment, not a cost.
Why do engineers ALWAYS lose budget battles to sales? Because we speak tech, while they speak MONEY. This is the exact framework I use to translate 'we need to refactor' into 'this will save us $2M/year' — complete with a ready-to-use ROI calculator.
How I engineered a hub-and-spoke platform for 3 massive mining sites in Borneo — real-time fleet management, automated HSE monitoring, and mine planning analytics that instantly caught fuel thieves in the very first month of deployment.
The hardest-working engineer isn't always the highest-paid. Data from Google, McKinsey, and DORA proves: those paid 3-5x more are often 'lazy' at coding but smart at leveraging systems. This is the framework shift from Maker to Multiplier.
Are you 'just' working on Jira tickets while other developers are shaping product decisions and leveling up 3x faster? Here is the framework that transformed me from a regular backend engineer into someone who owns business outcomes — with real-world production examples.
One lone engineer. ONE month. Now it's the invincible backbone for 4.1 million microfinance customers. The completely raw story of how I hand-coded an offline-first architecture for 5,000 field officers in Indonesia's deepest corners — and the brutal lessons of being a Single Point of Failure.
How I integrated a customer-facing app directly into Core Banking without middleware — serving millions of micro-finance customers with real-time accuracy, maintaining zero downtime even when traffic spiked 5x during Eid season.
