JOHN OK.

AI tends to automate tasks inside jobs rather than wipe out whole professions, and history (ATMs, spreadsheets, word processors) shows cheaper tools often expand demand. That story is true at the aggregate level and incomplete for most people. New jobs rarely go to the workers who lose the old ones, and productivity gains only become a lasting edge if you redesign work around AI rather than bolt it onto the old workflow. What matters more is a repricing of human value. As execution gets cheap, scarcity shifts toward judgment, accountability, trust, taste, relationships, and ownership. AI can raise production; who captures the gains depends on institutions and who owns the systems that produce the output. The useful question is less “how many jobs survive?” than “who owns the machines, and where do you sit in the value hierarchy when intelligence is abundant?”

The majority of developers work on projects. Some people work from a project that has amassed enough years, choices, setbacks, and identity that it no longer feels like software they created but rather a place they call home. This essay refers to this phenomena as the "Resident Project," a long-term personal endeavor that has transformed from artifact to environment, bearing the developer's skills as an archeological record, their values as an attention diagram, and their history as a palace of memories. The relationship is two-way: the project shapes the developer, and the developer shapes the project. The essay explores the path from tool to territory to home, looks at the pathologies that can turn habitation into incarceration, and makes the case that the Resident Project becomes more significant rather than less in a time when AI makes implementation commonplace: what a developer decides to spend years creating is becoming more and more of their most valuable asset.

Passion and niche are less something you find and more something you grow into through repeated contact with reality, filtered by honest self-knowledge. This framework is designed to accelerate that contact while keeping you grounded in who you actually are and what the current environment makes possible. Begin the Stage 1 inventory this week. Design your first experiment within 10–14 days.