index aaec704..f580c44 100644
@@ -14,11 +14,4 @@ hackathon judges have rubrics. if the rubric says "use of [sponsor API]" or "ali
## the fix
-read the judging criteria before you start building. seriously, read them. then build something that explicitly hits each criterion. you can still build what you're passionate about — just frame it within the track.
-
-## see also
-
-- [[perfectionism-over-hackathon-fit]] — building the right thing > building the perfect thing
-- [[not-reading-submission-requirements]] — same mistake: not reading the rules
-- [[frame-impact-explicitly]] — framing matters for judges
-- [[figure-out-what-you-want-before-partners]] — know what you're optimizing for
\ No newline at end of file
+read the judging criteria before you start building. seriously, read them. then build something that explicitly hits each criterion. you can still build what you're passionate about — just frame it within the track. this is the same mistake as [[not-reading-submission-requirements|not reading submission requirements]] — not reading the rules before playing the game. [[frame-impact-explicitly|frame your impact]] in terms of what judges care about, and make sure you [[figure-out-what-you-want-before-partners|know what you're optimizing for]] before you start.
\ No newline at end of file