Blog
Practical writing on Android development, software architecture, engineering leadership, and building better teams.
The exact Claude Code workflow I run on a client's Kotlin Android codebase: a per-project CLAUDE.md, a 3-minute context load, plan mode before production, and a session log that compounds over a long engagement.
n8n's default failure mode is a green success on a workflow that did nothing. Six silent traps from real self-hosted pipelines, each with the symptom, the failure underneath, and the fix that holds.
I gave Claude Code an expert council: a table of personas, each backed by live library docs via Context7, that it convenes during planning.
How to migrate off Lovable Cloud onto self-managed Supabase, a VPS, and Cloudflare DNS with zero customer-visible downtime. The four hardest pieces and the sequence that worked.
A pre-seed startup wanted to self-host Gemma 3 to save 5x before their raise. The math said otherwise. The real AI cost levers are not the provider: they are metering, caching, and cascading.
Custom Claude Code skills cost tokens on every turn, even the ones you don't invoke. Here's the router pattern that cut my catalog from 78 skills to 40 without losing a single workflow.
Android architecture 2025: Jetpack Compose + MVVM + Hilt is the recommended stack. Practitioner guide to migration from Fragments, pitfalls, and Kotlin.
Fractional CTO vs full-time CTO: compare cost, commitment, and coverage, then use a 5-question decision framework to pick the right model for your stage.
A fractional CTO is a senior engineering leader who works part-time with your startup. Here's when to hire one, what they do, and what to expect to pay.
AI-written code is efficient, but treating it as a magic bullet erodes skills and ships bugs. When to use AI, when to skip it, and how to keep it an assistant, not a crutch.
Pull requests can become a bottleneck in closed-source teams. Here is why, when to keep them, and how to move to code discussions without losing quality, speed, or trust.
Exceptional engineers can multiply a team's output. Here's what defines a 10x developer, and how to build and keep them through hiring, momentum, trust, and autonomy.
Messy code creeps in as teams and projects grow. Here are the warning signs that your codebase is deteriorating, and the concrete ways to get your developers back on track.
Java on Android is a red flag: it signals outdated practices and pushes good engineers away. Why Kotlin wins, and how to migrate to it incrementally without a risky rewrite.
No posts match this tag.
New deep-dives in the works. More on the way.
Want it in your inbox the moment it drops?