Forty hours can reveal whether an idea deserves more work. It cannot turn every weekend experiment into a finished product.
Damon Hernandez made that boundary clear in the 2018 Constructrr conversation: “It's called a hackathon and not a product buildathon for a reason.” He described the AEC Hackathon as a community where built-environment professionals and technologists could work on a real Monday problem without treating the weekend as live project delivery.
Saturday failure belonged before Monday delivery
Damon Hernandez said the event grew from a gap he had observed. People wanted to experiment with technology, but project schedules and budgets left little room to try, fail, and change direction.
The hackathon gave that learning a bounded place. Damon described teams spending most of a day on one path, abandoning it, and building something different overnight. The experiment could fail without asking an active project to absorb the same uncertainty.
Sharing was part of the ethic and part of the weakness
Damon described participants who opened their work so others in the industry could benefit. He was also candid that projects were often found through personal contacts, links, and word of mouth because the central reuse system was not strong enough.
That limit matters. A useful experiment can disappear if the result, failed approach, and next question are not recorded somewhere other people can find them.
Different roles changed the information in the room
Later, Damon Hernandez described teams that set company affiliation aside and focused on what each person could contribute. People from competing firms and different generations worked on the same problem.
The point is not that a mixed group automatically produces a better answer. It can surface owner, design, construction, technology, security, and facilities concerns early enough to shape what the group tests.
Public agencies could observe before funding another step
Damon also described public agencies bringing city problems to an event, seeing what practitioners could build, and sometimes supporting a pilot or more development. He explicitly did not promise participants funding. He kept the weekend separate from the work required to prove a solution in context.
Choose one Monday problem that is too uncertain to place directly into a live schedule. Give a cross-role group a protected test period. At the end, record what it tried, what failed, what remains unsafe or unresolved, and who decides whether another step is justified.
The weekend has done its job when the team leaves with clearer learning, not when it pretends an experiment is already a product.
