index e59b9ae..512041b 100644
@@ -12,15 +12,8 @@ teams spend hours setting up kubernetes, microservices, CI/CD pipelines, and dat
## why it's a gotcha
-over-engineering is a way to feel productive without making progress on what matters. nobody at a hackathon cares about your infrastructure. they care about whether it works and whether it solves the problem.
+over-engineering is a way to feel productive without making progress on what matters. nobody at a hackathon cares about your infrastructure. they care about whether it works and whether it solves the problem. at the feature level, this looks like [[building-all-in-one-product|building an all-in-one product]]; at the planning level, it looks like the [[over-planning-trap]].
## the fix
-use the simplest possible stack. sqlite, a single server, hardcoded config. get the demo working first. you can architect properly later if the project survives past the weekend.
-
-## see also
-
-- [[building-all-in-one-product]] — over-scoping at the feature level
-- [[over-planning-trap]] — over-engineering at the planning level
-- [[building-before-validating]] — building infrastructure for a problem nobody has
-- [[perfectionism-over-hackathon-fit]] — optimizing the wrong things
\ No newline at end of file
+use the simplest possible stack. sqlite, a single server, hardcoded config. get the demo working first. you can architect properly later if the project survives past the weekend. don't build infrastructure for a problem you haven't even [[building-before-validating|validated]] yet.
\ No newline at end of file