Six months, one proof of concept, and everything it taught a product team about agreements, failure and where engineers spend their time.

Asking AI instead of a teammate can solve the problem instantly, while quietly removing the small interactions through which teams built context and trust.

A deliberate chapter back in an IC role, and the delegation skills from managing people keep resurfacing in the daily mechanics of working with agents.

Technical depth still matters. What changed is that producing a plausible solution got cheaper, so execution is weaker evidence of the judgment behind it.

Entry-level work ran a loop that quietly produced senior judgment. AI shortens that loop, so teams have to build on purpose what they used to get free.

As AI makes implementation cheaper, product engineers grow by practising the product, writing, pricing, and distribution decisions their briefs omit.

Research finds women have a stronger preference for jobs with narrower salary ranges compared to men, and that this preference is associated with less assertive negotiation behaviors.

Building an AI harness for my team taught me that the tooling was only part of the work. The more important outcome was making our working agreements visible, discussable, and executable.

AI-driven productivity follows a predictable curve — boost, stretch, crash. Three operational limits help teams sustain intensity without burning through attention and judgment.

AI compresses delivery cycles, but trust and emotional processing don't. That gap — Human Latency — is the friction your team can't ship away.

AI is changing how we write code — but not why we build. A gentle, optimistic note for juniors and career switchers learning software today.

A practical, copy-pastable operating system for healthy, high-performing engineering teams in remote-first SaaS environments. Covers team operations, delivery, metrics, culture, and people growth.

A reflective recap of 2025 — choosing a pause, rebuilding capacity, returning to the market, and remembering that people are the point.

Ambition can look like strength from the outside — but for many high achievers in tech, success comes with a quiet emotional weight rarely seen or acknowledged.

When productivity stops being what we do and quietly becomes who we are — a reflection on identity, self-worth, and performance culture in tech.

Burnout doesn’t always arrive as collapse. Often it comes quietly — through numbness, over-functioning, and the slow fading of joy in work that once mattered deeply.

Fast, high-signal qual + quant reviews help triads reconnect with reality—turning scattered data, user feedback, and technical signals into shared judgment in just 45 minutes.

Shipping isn’t the finish line — it’s when the real signals start. How triads can use care windows to learn, restore coherence, and protect the team’s rhythm after each release.

Why ignoring design debt quietly drains product velocity — and trust. How Product, Design, and Engineering can recognize it early, address it together, and rebuild coherence without slowing down.

How triads can turn endless task lists into meaningful progress. Moving from backlog autopilot to intentional weekly bets that bring focus, ownership, and rhythm back to teams.

Cross-functional collaboration shouldn’t feel like a game of hand-offs. Here’s how Product, Design, and Engineering can move from alignment theatre to shared flow — building clarity, trust, and moment...

Overcommunication can look like alignment, but often it’s anxiety in disguise. Learn how to design remote communication that builds trust through clarity, not noise.

Understand how each person thinks and decides, then choose a management style that fits. A practical, people‑first guide with day‑to‑day styles, a lightweight personality map, and weekly rituals.

If I were to ask any random engineer, who didn’t have management experience, “what does your manager actually do?”, I bet they would say something along the lines of “well&#…

A practical, people‑first playbook for running remote 1:1s that build trust and psychological safety, surface risks early, and drive growth—without turning into therapy or status updates.

Career growth in software engineering isn’t just about writing better code—it’s about taking ownership of your trajectory and focusing on real-world impact.

Font Modifier - Experiment with variable fonts

Small, thoughtful ways to support each other at work can have a big impact. Normalizing simple signals—like Slack statuses or images—helps create a healthier, more mindful workplace.

Changing a field type in an Ecto embedded schema requires both a code update and a database migration. This guide walks through the process, ensuring data consistency and avoiding common pitfalls.