Hacker News new | ask | show | jobs
by albertgoeswoof 2968 days ago
> Week 7-11: Build, prototype, and validate your solution with prospective customers

> The time commitment is Sundays 12-6PM for twelve weeks in fall 2018

Is 24 hours really long enough to build something valuable, prototype it and validate it?

When I build things in my spare time it takes me way longer than that... but then I don't write code full time for a living so maybe I'm just slow...

3 comments

I think the usual approach with these 'sprint' methodologies is to use software like InVision, Figma, etc. to mock-up a prototype. No sense coding before you've got proof positive that users will care, the thinking goes.

See: http://www.gv.com/sprint/

Often times you don't have to build anything to validate an idea. Talk to potential users and get a commitment to pay for a product.
We anticipate that mileage will vary by team, and that we'll support teams to reach these milestones. This includes helping find those customers and prioritizing feature development.