Discussion

ASK HN: Help with how to breakdown a project

Let me start with - I am not a tech person at all.

I have a start-up web application that I need to build, and I'm looking to outsource the development of an initial prototype.

My question is this... is it better to break down the entire project into small milestones, or is it better to explain the entire project at once and work with the developer to create it all?

My gut tells me, break it down into small milestones that build upon each other. But, not being a tech person I don't know the answer to this next part...

as a developer are you able to work with small pieces of a project without knowing what is coming next? Is it easier to know the big picture so you can plan for what is coming up as you go?

I think of building a house.... I wouldn't want to build a basement and foundation of a house if I didn't know what the floorplan was? I could build a square foundation, but the house could be cirle? Same with this... I could tell a developer to build a registration page, but if he/she doesn't know what that info is for, it is going to work?

Thank you.

3 points ericseidelman 16 years ago 3 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton