Rebecca Powell

## Abstract Resilience is commonly evaluated through availability, fault tolerance, recovery time and the frequency of failure. These measures describe whether service remains operational and how quickly execution can be restored, but they do not fully de

I have spent far too long trying to answer what should have been a simple question: Should I keep my grandfathered GitHub Copilot Pro plan at $100 per year that runs out in December 2026, or move to Copilot Pro+ at $39 per month? At first glance, this loo

Temporal Nexus is one of the most interesting things in Temporal right now. If you are building distributed systems in .NET, it gives you a cleaner way to call cross-service or cross-namespace operations from workflows without dropping into ad-hoc HTTP or

Date: 5 July 2026 Repository checked: temporalio/sdk-dotnet on main and nexus-api-gen-signal-with-start Docs checked: Temporal .NET Nexus quickstart and feature guide Scope: Public preview Nexus support in the .NET SDK Executive summary The core idea is g

Retries are not durable execution. That sounds obvious when written down. But in real architecture conversations the distinction gets blurry very quickly. Someone says: We already have retries. We use exponential backoff. We have circuit breakers. We use

Part 8: The New Power Map This final chapter gathers the whole series into one question: after the bubble breaks, which layers actually own the durable value? If you are arriving here first, the cleanest entry point is still the preface, followed by Part

Part 7: After the Crash Part 6 described the convergence that breaks belief. This chapter follows the story through the crash and into the mature AI economy, where the first narrative has failed but the technology keeps spreading. It also sets up the fina

Part 6: Breaking Point Part 5 argued that AI changes not only software, but the cost structure of the firm itself. This chapter turns from structure to timing: what actually causes the market story to break. It is the hinge in the series, and the natural

Part 5: Firmware Part 4 argued that AI changes the economics of software. This chapter pushes the argument into organizational form: if software becomes easier to generate and workflows become easier to automate, the company itself starts changing shape.