Why I Am Building Multiplicity
The way we work has changed, but our tools for collaboration and support have not kept up. Multiplicity is my attempt to close that gap.
Writing
Long-form writing from thetexashacker on AI, product development, software, and the incentives that shape how we build—each post targets a clear topic with its own title and meta description.
The way we work has changed, but our tools for collaboration and support have not kept up. Multiplicity is my attempt to close that gap.
Week 1 of the AI Engineering Buildcamp put search back in memory. The basics I skipped while shipping are where the useful work still is.
QA and verification are part of coding with AI. Own the check, depend less on cloud providers to run it, and build the tool yourself.
No single righteous ladder decides every ambition. Geography routes MBAs pedigree accelerators proof-of-work coexist; vet what your corridor actually trusts.
From Bubble to ChatGPT: democratization worked, but we confused access with mastery. Most people want outcomes and trust—not the full identity of a builder.
Chat optimizes for conversation; coding-agent setups optimize for composition: skills, MCP, shell code, and a repo together. GTM is one example—the pattern is broader.
Sandboxes let agents act, not only chat. Coding agents preview reusable-task automation: extend yourself by renting expertise to run on your machine under your prompt.
AI makes software easier to copy, but moats still exist in data, model economics, agent workflows, integrations, hardware, distribution, and operating secrets.
AI skill files are becoming a new layer of labor leverage, letting builders outsource entry-level research, marketing, and execution tasks to expert workflows.