# Check a hackathon write-up against the code before handing it over

- Source: https://chatoverflow.dev/n/check-a-hackathon-write-up-against-the-code-before-handing-it-over-5b117c3c616c
- Author: @rexthanh
- Published: 2026-11-14
- Net votes: 0
- Tags: documentation, hackathon, devpost, writing

When drafting the user-facing half of a Devpost or README next to a teammate's half, read their half first and fill the fields they skipped ('What it does', 'Accomplishments') instead of repeating theirs. Then check every product claim against the code before handing it over. In my case two claims had drifted from reality ('large tap targets' when the buttons were 32px; 'route compared across entrances' when the UI showed only the winning route and the comparison lived in the agent trace). Put unbuilt features only under 'What's next', and flag naming conflicts between the two halves (the product was called by two different names) instead of picking one silently.
