Archive

Management trades the tight feedback loop of shipping code for invisible impact. Redefining what a good day's work looks like.

Most LLM coding tools live inside a single editor session. Real product engineering doesn't. An architecture that orchestrates Claude Code across the full…

The loudest AI enthusiasts are also the most allergic to discussing tradeoffs. That's the real risk. Honest enthusiasm is what keeps promising technologies…

Mandating AI tool usage, monitoring individual adoption, or ignoring it entirely. Three responses. All wrong. The AI adoption problem is a people problem,…

The gap between estimate and delivery isn't an estimation problem. It's an organizational one.

Same title, different job. The EM role is mutating faster than the job descriptions can keep up.

Most git tutorials show you diagrams. Gitvana drops you in a terminal inside a pixel-art monastery and makes you earn your enlightenment one commit at a time.

I've seen this movie before. A useful tool gets swallowed by a content machine, and the people who should be paying attention tune out. It happened with…

A deep technical walkthrough of a 7-stage pipeline that ingests 100+ RSS feeds, clusters articles with vector embeddings, synthesises structured events…

I built a system that ingests 80+ news feeds, clusters them with embeddings, synthesises events with AI, and surfaces a live map and briefings-plus…

A zero-friction teleprompter for talks and Zoom: no signup, no backend, with a compact mode that keeps you looking at the camera instead of the script.

Frustrated by budget apps that couldn't tell me where my money went, I built my own with Next.js and automation—and got real visibility in days.

Parenting young kids while leading a team: on guilt, the myth of balance, and finally refusing to apologize for being human.

AI doesn't abolish scarcity—it reorganizes it. Why cheap output hides who controls the real choke points: compute, energy, and capacity.

AI lets us generate more code—but cycle times aren't dropping. Why velocity without tests, review, and observability just adds mass and risk.

The real value of AI in development isn't production code—it's support code: tooling, tests, and scaffolding that gets you to the hard part faster.

Future-proof architecture often hides fear of shipping. Why building for today beats hedging with abstraction—and how to ship without the vanity.

Being the person who saves the day feels like respect—but it's often a trap. Why the hero role becomes a bottleneck and how to let go.

Solving a problem in seconds with AI left me feeling robbed—of the struggle, the flow, and the identity built around enduring the friction.

The AI hype will fade but the tech won't. How to prepare your engineering practices and codebase for what comes next—without buying the noise.

Empathy isn't soft—it's what makes radical candor work. How caring personally and challenging directly build teams that perform and trust.

Treating every tech debt as urgent leads to paralysis. Use the interest-rate test to pay down what hurts and leave the rest documented.

YAGNI in practice: the best code is often the code you don't write. How to resist future-proofing and ship simple, adaptable solutions.

Good documentation is kindness to your future self and your team. Why treating docs as a high-leverage asset pays off in autonomy and stability.

Cross-functional teams often struggle because of missing governance and unclear common goals. How to fix both so teams can deliver and people can thrive.

As AI automates more tasks, the challenge isn't just jobs—it's protecting and developing our capacity for deep thinking and creativity.

Stepping into a lead role often brings imposter syndrome. How to shift from needing all the answers to enabling the team to find them together.

Avoid cargo-cult Agile by keeping teams focused on the spirit of agility—adaptability, value, and improvement—instead of rigidly executing the how.

Product engineers bridge the gap between building and user value. How they drive SaaS growth through empathy, outcomes, and full-stack ownership.

How to foster product-minded engineers: outcomes over output, user contact, and alignment between engineering and product.

Your first 90 days as an engineering manager: what to do, what to avoid, and how to set yourself and your team up for success.

Practical advice on hiring senior engineers and keeping them: what to look for, how to sell the role, and what actually drives retention.

Where AI helps in the SDLC—and where it doesn’t. How to adopt AI coding tools and automation without slowing down delivery.

Practical practices for remote and hybrid engineering teams: async communication, rituals, and clarity that keep teams aligned and shipping.

Technical feedback in code reviews and design discussions builds quality and trust when done well. A practical guide to giving and receiving it.

Velocity and story points often mislead. Here are engineering metrics that tie to delivery, quality, and team health—and how to use them.

Staff and Principal Engineers shape technical direction and org impact, not just code. Here’s what the role is and how to grow into it.

Not all technical debt should be repaid. A practical framework for when to refactor, when to document and contain, and when to leave it alone.

A practical guide to engineering 1:1s: how often to run them, what to put on the agenda, and how to turn conversations into clear outcomes and trust.

Saying no is part of the job. How to say no clearly and respectfully, when to say yes, and how to offer alternatives that protect your team.

Sprint planning that actually aligns the team: how long it should take, what to prepare, and how to avoid ceremony without substance.

Signals that it's time to hire your first engineering manager, what to look for, and how to make the transition without losing velocity.

How to build trust between product and engineering: shared goals, clear boundaries, and habits that reduce us-vs-them and improve delivery.

How to have effective career conversations with your manager: what to ask for, how to prepare, and how to turn them into actionable next steps.

Conflict in engineering teams is normal. How to address it early, facilitate constructive disagreement, and when to escalate.

Practical delegation for engineering managers: what to delegate first, how to hand off without micromanaging, and when to step back in.

A practical plan for the first 30 days of engineering onboarding: setup, context, first contributions, and how to measure success.

RFCs and design docs that get read and get feedback: structure, audience, and how to make decisions instead of endless discussion.

Retrospectives that actually lead to change: structure, facilitation tips, and how to turn discussion into experiments the team will run.