Three opinions, in full.

01 · Product and engineering are one discipline.

The textbook version of software engineering was written for a world where someone else — a PM, a designer, a product lead — decided what to build, and engineers implemented it. That world is ending. Agents accelerate the implementation so much that the bottleneck moves back to the decision: what is actually worth building, for whom, and against what bet?

At startup scale, that wall was never real to begin with. The technical founder is the product manager is the architect is the on-call. This site teaches the unified practice from the engineer's side — not because engineering is more important, but because it is the side where most of the writing is wrong for the startup case.

02 · Startup engineering is the hardest engineering.

Everyone agrees that Google-scale problems are hard. Fewer people admit that building at startup-scale — five engineers, two hundred users, six months of runway — is harder in a specific, measurable way: every decision costs more, because you can't afford to redo it.

The skills on this site are not a simplified version of enterprise engineering. They are a different thing: the judgment calls that make small teams look fast. What to cut. What to defer. What to do properly the first time because the second time will kill you.

03 · Knowledge is free. Judgment is the product.

Anyone can write a tutorial on TDD. There are a hundred of them. What compounds over a career is knowing, at 11pm with half the data, which decision to make. That judgment cannot be googled.

Every skill on this site is a piece of judgment encoded as a prompt — so an agent working alongside you, on a Tuesday afternoon, can reach the same decision I would reach. That is the product.