Writing
Deep-dives on software architecture and the way source code is structured — written to be understood by beginners, yet useful to teams shipping at scale. Diagrams, real examples, no hand-waving.
A calm guide to managing up with non-technical leadership: translating technical work into risk, options, impact, timing, and decisions without hiding complexity or talking down to people.
A practical look at AI agents beyond the hype: what changes when models can use tools, follow workflows, remember context, ask for approval, and produce auditable work, plus where human judgment still matters.
A reflective essay on why side projects matter without turning them into hustle: small experiments, learning loops, creative ownership, career signals, and the quiet confidence that comes from building something end to end.
A practical reflection on feature flags: how they decouple deploy from release, support gradual rollout and kill switches, and what teams must do to avoid flag debt, hidden complexity, and weak observability.
A practical explanation of database sharding: what changes when one database is split into smaller partitions, when sharding is worth the operational cost, and why shard keys, hotspots, rebalancing, and observability matter.
A calm reflection on performance reviews that actually help people grow: using evidence, expectations, calibration, feedback, and follow-through without turning the review into a surprise or a ritual.
A practical article on data privacy in AI work: how prompts, documents, logs, retrieval, training, and evaluation create new data paths, and how teams can use AI while keeping consent, minimization, access, and retention clear.
A reflective essay on moving into tech or through a major technology shift: learning the language, rebuilding confidence, using past experience, and treating the transition as quiet practice rather than a sudden identity change.
A practical explanation of Continuous Integration and Continuous Delivery: how CI protects shared code, how CD keeps releases ready, and why tests, trunk habits, feature flags, and deployment discipline matter.
