The fundamental technology, economic, and organizational inquiries that drive our research, canonical writing, published books, and software engineering. Rather than accepting industry orthodoxy, we evaluate each problem from first principles in plain English.
First Principles • How We Formulate Questions
Questioning the Software Industry's Costly Defaults
Much of what the technology industry accepts as standard practice is actually cargo-cult dogma. Large software companies regularly spend hundreds of millions of dollars building massive distributed clusters to do jobs that could easily run on a single $150 computer. They hire hundreds of engineers to build features that a three-person team could deliver in a month.
By asking foundational questions about physics, economics, and human communication, we strip away the bloat. Below are the six core questions that guide everything we build, write, and teach.
Inquiry 1 • Engineering Leverage & Team Topology
How can a small team of 5 to 10 builders build systems that serve millions?
Software is the highest-leverage medium ever invented. When an engineer writes zero-dependency code that runs in fast computer memory, a single server can process tens of thousands of requests per second without sweating. Adding more people to a software team creates communication drag (governed by the formula n(n-1)/2). Five sovereign builders with clear ownership and two-page decision memos will reliably out-ship fifty corporate engineers burdened by endless alignment meetings.
First-Principles Answer: Keep teams at 5 or fewer per repository, ban recurring status meetings, and enforce end-to-end technical ownership with zero external runtime bloat.
Inquiry 2 • Hardware Physics & Latency
Why do computer systems feel slower even as processors get faster?
Silicon chips run billions of cycles per second, but modern software stacks add hundreds of nested abstraction layers, bloated packages, and repeated round-trips to disk and distant databases. Reading data from computer RAM takes roughly 100 nanoseconds, while reading from a solid-state disk takes 100 microseconds, and an unindexed database query over a network takes 150 milliseconds. When software keeps active data in fast computer memory (RAM), queries finish in a fraction of a millisecond.
First-Principles Answer: Eliminate slow disk reads from the active path. Keep active working data in fast computer memory to guarantee instant responses.
Inquiry 3 • Cloud Economics & FinOps
Why do enterprises waste 30% to 50% of their cloud budgets, and how do we stop it?
Cloud providers make money when customers leave idle instances running. Engineers provision oversized 64-core virtual machines to handle rare traffic spikes, then forget about staging clusters and abandoned elastic block storage volumes. Our verified $12,000,000 enterprise audit proved that cloud waste is an organizational failure: nobody owns the bill. Rightsizing compute, automating staging shutdowns, and migrating steady baseline workloads to leased bare-metal infrastructure saves millions.
First-Principles Answer: Audit monthly billing line by line, rightsize instances to match real p95 utilization, and use cloud elasticity only for unpredictable spikes.
Inquiry 4 • AI Safety & Multi-Agent Consensus
How can we trust autonomous AI agents with high-stakes financial and medical workflows?
Generative language models are probabilistic token predictors, not deductive truth engines. When deployed in isolation, they hallucinate facts, make mathematical calculation errors, and accept poisoned prompts. Safe autonomous systems require Byzantine fault-tolerant architecture: three independent models from distinct model families cross-checking outputs through strict cryptographic consensus gates before any database write or financial transfer executes.
First-Principles Answer: Never trust a solitary model. Implement 2-of-3 Byzantine consensus gates where adversarial validator agents review all proposed modifications.
Inquiry 5 • Technical Communication & Writing
Why is plain-English writing the highest-leverage skill an engineer can possess?
Technical jargon is frequently used to mask intellectual insecurity or incomplete thinking. If an architect cannot explain a system design to an intelligent fifth-grader without using acronyms, they do not yet fully understand it. Clear writing forces logical clarity. A two-page decision memo written in simple prose aligns cross-functional stakeholders, prevents months of redundant code rewrites, and scales an engineer's influence across an entire organization.
First-Principles Answer: Write everything in 5th-grade plain English. Ban buzzwords, quantify all trade-offs, and limit architectural proposals to two printed sheets.
Inquiry 6 • Owning Your Technology
How do we build software platforms that outlive external vendor dependencies?
Modern web development has developed an unhealthy dependency on third-party SaaS services, cloud databases, and closed proprietary frameworks. When a vendor hikes prices or deprecates an API, whole companies scramble to rewrite their stack. By building on standard open protocols, compiling to static edge files, and utilizing vanilla JavaScript and SQLite, an engineering platform can run reliably for twenty years at almost zero maintenance cost.
First-Principles Answer: Choose boring, battle-tested technologies. Favor plain text, static files, and portable databases over vendor-locked proprietary clouds.