Writing

Have you ever had the feeling that while you're crossing things off your never-ending to-do lists, you're not really moving closer to your major objectives? You may be conflating planning with strategy. Despite their frequent interchangeability, they have completely different functions. Strategy is your compass; it's how you pick your overall course, deal with turmoil, and adjust to ambiguity. Planning is your road map; it's the careful, methodical execution required to establish order and truly arrive at your goal. In the end, both are necessary for actual success: strategy makes sure you're climbing the correct mountain, and planning gives you the precise steps to reach the summit.

Visual aggression is the enemy of thought. Here is why I prioritize text over everything else.

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.

Every major product failure, failed acquisition, and bombed franchise follows one of five patterns , and they all share the same root cause: a creator who stopped looking outward and started looking inward. This article breaks down those five traps (ignoring why existing systems work, cannibalizing your core product to chase new audiences, confusing your user's identity needs, centering yourself instead of your customer, and refusing honest market feedback) through the lens of real business disasters and wins ; from Ron Johnson's implosion at J.C. Penney to Domino's improbable comeback, from New Coke to the Cayenne. The argument is simple: confidence is what makes you build; discipline about who you're building for is what makes it last.

Every profession seems to have its own "thinking" now, design thinking, systems thinking, product thinking, critical thinking. This article traces where that pattern comes from. It turns out that pairing "thinking" with another word does something specific in both directions: the modifier gives thinking a track to run on, and "thinking" transforms the modifier from a noun into a methodology. Underneath the branding, these frameworks all share a common purpose, they are structured tools for forcing the kind of slow, deliberate mental effort the brain actively tries to avoid. The article breaks down why this linguistic trend has taken over professional life, what three contrasting examples reveal about how these frameworks actually work, and offers a five-question tool for decoding any new "X thinking" term you encounter.

End-to-end encryption protects message content but leaves metadata such as identities, IP addresses, and contact patterns visible to network observers. This piece compares six chat apps by how much metadata they remove, using the LINDDUN framework of identifiability, linkability, and detectability: Signal's centralized encryption, Session's decentralized onion routing, SimpleX's identifier-free queues, Keet's serverless peer-to-peer connections, Cwtch's Tor-only routing, and Briar's offline mesh. No single app suits everyone. Each one trades privacy guarantees against everyday convenience, so the right pick depends on your threat model.

1. Reducing software installer size does not equal reducing memory usage at runtime 2. WebAssembly enables compiled languages to bypass JavaScript performance bottlenecks in the browser 3. Progressive Web Apps solve the user's psychological need for "installable" software without desktop bloat 4. Frameworks like Tauri fix distribution bloat but still rely on resource-heavy system webviews 5. Hardware constraints force developers to understand the true architectural cost of their tools