<![CDATA[Beaver Duty]]>https://www.beaverduty.comhttps://substackcdn.com/image/fetch/$s_!kDd-!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdad08adb-cec4-40bc-b6dd-e00248fc3fda_1280x1280.pngBeaver Dutyhttps://www.beaverduty.comSubstackThu, 16 Apr 2026 11:59:54 GMT<![CDATA[Don’t be a hero]]>https://www.beaverduty.com/p/dont-be-a-herohttps://www.beaverduty.com/p/dont-be-a-heroFri, 30 Jan 2026 12:01:24 GMT

Every organization has a hero.

The engineer who knows how to restart the stuck pipeline. The one who gets pinged when the dashboard looks wrong. The person who quietly fixes things before anyone notices there was a problem.

Subscribe now

They are praised for being reliable, trusted for “always being there,” and celebrated for keeping the system running when it shouldn’…

Read more

]]><![CDATA[The trust gap in Data teams]]>https://www.beaverduty.com/p/the-trust-gap-in-data-teamshttps://www.beaverduty.com/p/the-trust-gap-in-data-teamsFri, 16 Jan 2026 12:01:57 GMT

Data teams live by SLAs and data quality checks. Yet almost no one actually trusts them.

Subscribe now

You can publish a beautiful document with freshness guarantees, pipeline success rates, and expected delivery windows, but the business will still check with you before using a dashboard. Because experience taught them that reality rarely matches the doc.

Why?

Because …

Read more

]]><![CDATA[Logs of Duty: Migration projects]]>https://www.beaverduty.com/p/logs-of-duty-migration-projectshttps://www.beaverduty.com/p/logs-of-duty-migration-projectsFri, 09 Jan 2026 12:01:22 GMT

Rule #1: A rewrite is a migration. Rewrites are scary. Migrations sound safer. So always label rewrite work as migration, even when you’re changing languages, data models, and mental health.

Subscribe now

Rule #2: Don’t spend too much time planning. Let the target architecture emerge organically through half-finished diagrams. Anyway, the plan will quickly become outd…

Read more

]]><![CDATA[Governance: Great intentions, bad outcomes]]>https://www.beaverduty.com/p/governance-great-intentions-bad-outcomeshttps://www.beaverduty.com/p/governance-great-intentions-bad-outcomesFri, 02 Jan 2026 12:01:06 GMT

Governance is key to engineering. It automates checks, removes human error, and ships faster with more consistency and less debate. In theory, security requirements are built into pipelines, compliance rules serve as guardrails, and engineers receive instant feedback instead of waiting for reviews.

Subscribe now

Platform and SRE teams love the clarity. Leadership love…

Read more

]]><![CDATA[Logs of Duty: System Ownership]]>https://www.beaverduty.com/p/logs-of-duty-system-ownershiphttps://www.beaverduty.com/p/logs-of-duty-system-ownershipSat, 27 Dec 2025 12:00:53 GMT

Rule #1: Assume it is not you. If your changes break something, it’s not your problem, it’s the owner who didn’t review carefully enough.

Subscribe now

Rule #2: Ask who the owner is in Slack. And enjoy watching three teams tag three other teams.

Rule #3: Check the Git history. The last commit was six months ago by someone who has already left the company. So is code re…

Read more

]]><![CDATA[Metrics without meaning]]>https://www.beaverduty.com/p/metrics-without-meaninghttps://www.beaverduty.com/p/metrics-without-meaningFri, 19 Dec 2025 12:01:41 GMT

Everyone wants to be data-driven.

Every team has dashboards, KPIs, and OKRs. A way to quantify progress, justify priorities, and demonstrate impact. The paradox? The more we measure, the less we seem to understand.

Subscribe now

Dashboards multiply, KPIs are updated quarterly, but rarely questioned, and we optimize for what’s easy to measure: deployment frequency, upt…

Read more

]]><![CDATA[Logs of Duty: Disaster Recovery]]>https://www.beaverduty.com/p/logs-of-duty-disaster-recoveryhttps://www.beaverduty.com/p/logs-of-duty-disaster-recoverySat, 13 Dec 2025 12:01:03 GMT

Rule #1: Write a disaster recovery plan. Make it a beautiful 20-page document. Store it in Confluence, and start telling everyone you’re ready to handle any disaster. With a bit of hope, you will never have to prove it.

Subscribe now

Rule #2: It should be okay to skip some components. There is no GPU in the DR region you have picked? Conveniently forget to mention it,…

Read more

]]><![CDATA[Another year, another migration]]>https://www.beaverduty.com/p/another-year-another-migrationhttps://www.beaverduty.com/p/another-year-another-migrationSun, 07 Dec 2025 12:02:52 GMT

“Urgent! PLEASE ATTEND: Next year’s strategy.”

We’re so used to inefficient calls with our manager that he now labels them for us. It’s thoughtful.

So, let’s join.

Subscribe now

As usual: big goals, big impact, big dreams. He talks with passion. And he loves seeing smiles on our faces. What he doesn’t know is that if we’re smiling, it’s because we’re commenting live and…

Read more

]]><![CDATA[AI models are the new technical debt]]>https://www.beaverduty.com/p/ai-models-are-the-new-technical-debthttps://www.beaverduty.com/p/ai-models-are-the-new-technical-debtFri, 05 Dec 2025 12:03:31 GMT

AI is the new north star for many organizations. Every roadmap, strategy, and investment deck now features some form of machine learning or generative intelligence.

Subscribe now

AI has become every organization’s new north star, the centerpiece of strategies and roadmaps. However, after the initial excitement, the implementation evolves into something familiar: shor…

Read more

]]><![CDATA[Logs of Duty: The onboarding]]>https://www.beaverduty.com/p/logs-of-duty-the-onboardinghttps://www.beaverduty.com/p/logs-of-duty-the-onboardingSun, 30 Nov 2025 12:01:25 GMT

Rule #1: Give them your curated docs collection. 57 pages of “Must Read.” Half of it is outdated. The other half, you have no idea as you never read them. Don’t forget to ask them to update the docs if they see any mistake.

Subscribe now

Rule #2: Assign a buddy who’s also new. Nothing builds team spirit like two confused people. But it’s company policy in order to val…

Read more

]]><![CDATA[Memory loss: The leading cause of workplace accidents]]>https://www.beaverduty.com/p/memory-loss-the-leading-cause-ofhttps://www.beaverduty.com/p/memory-loss-the-leading-cause-ofSun, 23 Nov 2025 12:02:58 GMT

The most significant health risk at work is memory loss. The middle management layer is at a higher risk than the others.

After months of hinting at the financial consequences of a project delay, I finally caught the attention of a few teammates on the matter. And they succeeded where I failed: in holding managers accountable.

Subscribe now

The secret?

Getting two manag…

Read more

]]><![CDATA[The invisible work that keeps everything running]]>https://www.beaverduty.com/p/the-invisible-work-that-keeps-everythinghttps://www.beaverduty.com/p/the-invisible-work-that-keeps-everythingFri, 21 Nov 2025 12:01:18 GMT

Some of the most impactful engineering work is also the least visible.

How do you link efforts to prevent incidents to outages that never happened?

How do you highlight incidents that were resolved in minutes instead of hours, thanks to your recent work?

How do you quantify the stress avoided because services became easier to deploy?

Subscribe now

What we see are feature…

Read more

]]><![CDATA[Logs of Duty: The Knowledge transfer]]>https://www.beaverduty.com/p/logs-of-duty-the-knowledge-transferhttps://www.beaverduty.com/p/logs-of-duty-the-knowledge-transferSun, 16 Nov 2025 12:02:35 GMT

Rule #1: Get informed two days before Steve leaves. That gives you plenty of time to absorb years of wisdom, undocumented bash scripts, and subtle deployment rituals. More time would trigger procrastination.

Subscribe now

Rule #2: Book one long meeting. Four hours on a Friday afternoon should do it. There is never enough time to share all the company gossip. Plan to o…

Read more

]]><![CDATA[1h47]]>https://www.beaverduty.com/p/1h47https://www.beaverduty.com/p/1h47Sun, 09 Nov 2025 12:01:40 GMT

1h47.

We messed up.

Our customers stared at a loading spinner for 1h47 while we tried to figure out what happened.

Subscribe now

As usual, triggered by toggling a feature bug flag.

But this time, the recovery took too long, and it’s not acceptable. What an idea to play with the toggles on a Friday evening!

The boss steps in for the post-mortem.

All the company's senior …

Read more

]]><![CDATA[Engineering without empathy: Why internal platforms fail their users]]>https://www.beaverduty.com/p/engineering-without-empathy-why-internalhttps://www.beaverduty.com/p/engineering-without-empathy-why-internalFri, 07 Nov 2025 12:03:14 GMT

Internal platforms were supposed to make engineering faster, safer, and more consistent. They promised to remove friction, automate pipelines, and create self-service environments for every developer.

Subscribe now

Taking a step back, would you confidently say the platform you are building or using has achieved these goals?

In many organizations, the opposite happened.…

Read more

]]><![CDATA[Logs of Duty: Write a runbook]]>https://www.beaverduty.com/p/logs-of-duty-write-a-runbookhttps://www.beaverduty.com/p/logs-of-duty-write-a-runbookSun, 02 Nov 2025 12:00:32 GMT

Rule #1: Start with a random template. If filling it out feels like a tax return, you’re doing it right.

Subscribe now

Rule #2: Showcase your Shakespeare writing skills. At 3 am, people will enjoy Googling the meaning of every word before acting. It’s never too late to improve your writing skills.

Rule #3: Document everything. Include architecture diagrams, system hist…

Read more

]]><![CDATA[AI dreams, corporate realities]]>https://www.beaverduty.com/p/ai-dreams-corporate-realitieshttps://www.beaverduty.com/p/ai-dreams-corporate-realitiesSun, 26 Oct 2025 12:01:43 GMT

Today is a big day. I finally hope to get an answer to the question I’ve been asking for three months: Can our organization support a new vector database?

Subscribe now

It all started when our team was asked to build a small internal app using LLMs. The purpose? To support our Chief Product Officer in his glamorous claims of leading an AI product.

The problem? We don’t…

Read more

]]><![CDATA[When Data democratization becomes data anarchy]]>https://www.beaverduty.com/p/when-data-democratization-becomeshttps://www.beaverduty.com/p/when-data-democratization-becomesFri, 24 Oct 2025 12:01:01 GMT

Data democratization was supposed to solve the bottlenecks. Instead of waiting days for an analyst to build a report, business users could query data directly, explore insights, and make faster decisions. Tools promised simplicity, dashboards promised clarity. Now, AI promises to answer every data question.

Unfortunately, it is not that simple.

Subscribe now

As more te…

Read more

]]><![CDATA[Logs of Duty: The Retrospective]]>https://www.beaverduty.com/p/logs-of-duty-the-retrospectivehttps://www.beaverduty.com/p/logs-of-duty-the-retrospectiveSun, 19 Oct 2025 12:02:31 GMT

Rule #1: Start with good vibes only. Open the meeting with “Let’s focus on the positives!” and watch everyone freeze, unsure of what to talk about.

Subscribe now

Rule #2: Celebrate that you’re having a retro. Even when the team has been fighting a SEV-1 for the past ten hours.

Rule #3: Timebox complaints. If someone dares mention a real issue, thank them for their inpu…

Read more

]]><![CDATA[The Reliability Leaderboard]]>https://www.beaverduty.com/p/the-reliability-leaderboardhttps://www.beaverduty.com/p/the-reliability-leaderboardMon, 13 Oct 2025 12:02:51 GMT

Today is deployment day.

I’ve been nominated to oversee the deployment of one of our microservices for two reasons:

  1. I’m currently ranking first in the reliability leaderboard! There has been no incident under my watch for the past month. (Don’t be impressed, I’ve just returned from a three-week leave.)

  2. This microservice has famously failed every deployment…

Read more

]]>