Blog

Most companies can tell you how many AI licenses they bought. Far fewer can tell you what changed because of them.

Three things to add before you hire your first engineer

Why your first engineering hire matters more than your next funding round

Two engineers asked me the same question last week: is a tech career still worth it in 2026? Here is how I answered.

Everyone talks about AI and the rise of small teams as if it’s a brand-new thing. It’s not.

A quick guide to heartbeat metrics (and why your dashboards won’t save you)

Hosted models, clean data, clear goals. The practical AI strategy that doesn't need a research team or a roadmap deck.

Data is not always smarter than experienced judgment. Three rules for knowing which to trust on a given product decision.

Developers shouldn't wait for product to hand them specs. How engineers can be part of discovery without becoming product managers.

A good place to start? Use the Eisenhower Matrix. This framework helps you categorize tasks and initiatives based on urgency and importance, making it easier to prioritize, delegate, or eliminate them

Estimates set a clear focus. Without them, teams can fall into the trap of endless tweaks and refinements.

When your company needs new software or to replace an existing one, this framework will help you make the right decision.

I built a working Slack bot that detects PII in messages without writing any code. The prompts, the steps, and what AI-assisted shipping actually looks like.

When your engineering team grows past 15 people, technical decisions stop happening in the room. RFCs are how you keep them visible without slowing them down.

Why companies are quietly moving back out of the cloud, and three architectural decisions that make your bill predictable enough to plan around.

Continuous delivery is a business call, not an engineering one. Your team's release frequency is set by leadership's appetite for risk, not by your CI pipeline.

Skip Redshift. Skip the data mesh. The serverless setup that gets a small startup to real analytics without three months of platform work.

A simple impact/effort/risk matrix to decide what your engineering team should build next, and what to say no to.

How to build career levels at a startup that don't feel like big-company levels in disguise. Pillars, principles, and the trap of copying a corporate framework.

Nada Kalo Ćukalović on why 'just be more open' is the wrong instruction for teams that don't feel safe, and what to do instead.

OKRs die in the spreadsheet between the kickoff and the review. Three lightweight check-in patterns that catch off-track key results in week four, not week twelve.

Monica, Head of Engineering at Beyond, on how she runs the first 90 days in a new company. The framework, the diagnostic, and the mistake she stopped making.

CliftonStrengths and a 15-minute exercise to find out how your teammates actually want to be managed. Useful for any team that has hit the 'why don't they just talk to each other' wall.

Stephan, an executive coach with 25 years in tech, on when career coaching is worth the time and when it is not.

How to evaluate engineers on more than one axis. The nine-box framework for matching development plans to where someone actually is in their career.

Your team is shipping every week and you still don't know if you're doing a good job. The difference between efficiency and effectiveness, and which one matters for leaders.