Three constraints before I build anything

A veteran builder dropped three bold rules: keep every idea to one page, make the core tech separable (build reusable know‑how, not just a product), and pick one defining constraint that gives the product its identity—think Minecraft is all blocks, IKEA is flat‑pack. The crowd? Mostly clapping. One fan basically confessed they’ve been doing this without realizing it, while others called constraints the secret sauce behind elegant solutions. But the fun twist: one commenter vowed to use the rules on a kitchen renovation, turning “startup playbook” into “home makeover hack,” and the thread ran with it like a meme—“one‑pager or no cabinets.”

Then came the spice. A skeptic jabbed the boldest rule—“separate core tech from product”—by pointing at LLMs (AI that predicts words): if the century’s biggest product is the tech itself, does the rule break? Cue eyebrow raises and caveats. Another commenter reframed it all as “product primitives,” those simple building blocks users interact with—blocks in Notion, tweets on Twitter—which gave the whole debate a glossary and a vibe. The verdict from the bleachers: constraints = clarity, but beware commandments that don’t fit every era. The drama wasn’t flames, but it sizzled: discipline vs. disruption, kitchens vs. code, and a growing cult of the one‑page north star.