Birthright Citizenship Ruling
A reflection on the Supreme Court's birthright citizenship ruling and what it says about America.
All of my posts.
A reflection on the Supreme Court's birthright citizenship ruling and what it says about America.
Agent skills are more than prompt folders: they are part of a deterministic shell around a stochastic model. This post walks through two ariadne patterns, skill binaries and dynamic skills, that keep that shell testable, maintainable, and in sync with the codebase.
AI is powerful, but it is not an oracle. It does not have a magic wand to create what you want exactly. You own the possibilities, and leverage AI to help at many different altitudes. Here's a concrete example of how I wrote the blog about space data centers. AI is the MATLAB, the Wikipedia, the Excel, the search engine, all packaged into a single tool that you can customize and extend. The capability is there; the human/AI interaction is still being sorted out.
With SpaceX IPO looming, let's take a look at the case of space data center, how realistic it is. As I poked around, I realize it's a matter of time before we run data centers in space, and that we really DO need Starship to pull it off economically. That is, if we look at the problem in the time frame of decades.
In the era of AI, your personal data can be a lot more valuable to you, as an individual.
Saturday morning, before exercise, I asked Claude one stray question. By afternoon there was a new repo, a pensive, four issues, and a working tool I'm using to write this post.
What is an AI Native Company?
Two weeks of building the substrate underneath an AI-native personal workflow: a base agentic development environment, a personal data access layer, a credential gateway, and a private canvas where ideas form, collide, and grow. Not ready for release yet — here's a sneak peek.
Moving to an Astro based new home for my personal blog. And a new location.
Adding tool calls to Parley on a flight, watching Claude make a mess, then drawing the architecture boundary for Claude and watching it execute flawlessly within it. The eureka: Claude Code is the execution harness, Parley is the interface for human to inspect and influence — both running on the same shared filesystem state.
A close read of the EDPB's €225M WhatsApp fine. The fine is a catch-22 for technical companies, that you need to write your privacy notice concise and easy to understand enough for laymen, yet need to be comprehensive enough to cover all basis. An extremely bad example of regulatory overreach, lacking resemblance of proportionality
Reflecting on a year of tinkering and adapting to the ever changing world of AI. After a year and 400+ commits on Parley.nvim, I'm convinced the future is humans setting up the environment, with full automation of the coding inside it. Here's my journey so far.
When agentic coding lets a vim user write a custom mouse-aware floating picker because Telescope couldn't do that. The implication for SaaS: programmability stops being a nice-to-have, it becomes the moat.
An iterative spec flow built on a small Makefile and a handful of markdown files — issue, todo, lessons, specs — cuts through the opaque magic of workflow tools. The trick is treating specs as sketches that bound the agent's search space, not exact behavior to confine it. Let AI bringing in world's knowledge!
The week of February 23, 2026: Dorsey's layoffs, Cloudflare's one-engineer Next.js rewrite, Karpathy's tweet. Picking up Conductor, OpenCode, and OpenSpec over a weekend and shipping 15K lines on Parley — agentic coding is no longer the toy it was ten months ago.
LLMs are fundamentally stochastic, but that's not new — the whole ML field always was, and it worked. The interesting question is how to ground stochastic computation in deterministic domains. Two paths: build a deterministic shell around the model (coding), or apply it directly where the domain itself tolerates noise (recruiting, marketing, design).
Mainstream type systems are simultaneously too strong (closed-world assumptions hurt during change) and too weak (can't say "positive integer" or "age between 0 and 200"). For startups in unsettled domains, duck typing wins — types are a luxury you afford after product-market fit.
Two quotes about data and intuition. "I trust your data, and my intuition" subtly inverts the knowledge hierarchy and subjugates domain expertise to authority. Bezos's version — when anecdotes disagree with data, investigate the measurement — is the better instinct.
Eight questions to ask before introducing a new process. People overestimate how much process helps, underestimate the cost of maintaining it, and assume it'll work just because it exists. And remember, processes rarely die on their own — the ritual often outlives the purpose.
Judgment slips when decisions become emotional — when you're defending a person, a past call, or a principle rather than solving the problem in front of you. Four signals to watch for in yourself, and four ways to guard against them.
Notes from the IEEPA tariff oral arguments. "Regulate importation" can plausibly mean tariff — but the power to tax is squarely Congress's, the Major Questions and Non-Delegation Doctrines bite, and the one-way ratchet of presidential power makes this near-unanimous against the administration.
Notes from judging a high school parliamentary debate. The opposing side isn't an adversary, it's a collaborator in a joint quest for truth — and the kitchen-sink approach loses on me every time. Logos 70%, ethos 20%, pathos 10%.
Andrew Grove treats management as a production system, but the deeper claim is that information workers are managers — their raw material is information, their output is influence. In modern Big Tech, being "a manager" isn't a promotion. It's just different work.
Read narrowly, Wong Kim Ark's actual holding only covers children of permanent legal residents. For 127 years, every branch followed the broader dicta instead — until now. A close reading of holding versus dicta, reliance interest, and what the Court is likely to do.
Healthcare's fragmentation isn't an accident — it's federalism plus misaligned incentives, where EHR vendors profit by locking customers in. NexHealth's Synchronizer attacks the problem at the technical layer, with the law (and a recent 4th Circuit ruling) on its side, eventually.