Comment by FinnLobsien

I think constraints essentially force you to reevaluate the thing from base principles because you add a condition that’s incompatible with the default way of doing things.

I think this is also why hackathons work: You can’t afford the bikeshedding we often do to avoid the hard work because you need to ship something by a deadline 1/500th of most of your normal deadlines, so all of your effort is concentrated into what moves the core work forward.

What gets proven in hackathons often become features, products, or companies later - even if they’re things that would be ruled out in any planning meeting because they seem too hard/laborious.