index 10c7e2f..07befde 100644
@@ -10,16 +10,8 @@ lesson from finding partner in hackathon is that you gotta figure out what you w
## why it's a gotcha
-if you don't know whether you want to win, learn, network, or ship, you'll end up on a team optimized for a different goal. the person who wants to win will clash with the person who wants to learn. both are valid — but they don't mix well under time pressure.
+if you don't know whether you want to win, learn, network, or ship, you'll end up on a team optimized for a different goal. the person who wants to win will clash with the person who wants to learn. both are valid — but they don't mix well under time pressure. the downstream effect is [[teams-without-shared-understanding|a team without shared understanding]], and under pressure, the [[personality-mismatch-under-pressure|personality clashes]] get ugly fast.
## the fix
-before the hackathon, ask yourself: am i here to win, learn something specific, meet people, or build something real? then find people aligned with that goal. it's a simple filter that prevents most team friction.
-
-## see also
-
-- [[teams-without-shared-understanding]] — the downstream effect of unaligned goals
-- [[unclear-roles]] — roles should follow from goals
-- [[solo-vs-bad-team]] — if you can't find aligned people, go solo
-- [[fomo-trap]] — FOMO can push you into the wrong team
-- [[match-the-theme-track]] — know what game you're playing
\ No newline at end of file
+before the hackathon, ask yourself: am i here to win, learn something specific, meet people, or build something real? then find people aligned with that goal. [[unclear-roles|roles should follow from goals]] — and so should your choice of theme or track. make sure you [[match-the-theme-track|know what game you're playing]]. if you can't find aligned people, [[solo-vs-bad-team|going solo]] is better than joining the wrong team out of [[fomo-trap|FOMO]].
\ No newline at end of file