|
|
|
|
|
|
by eggsnbacon1
2184 days ago
|
|
|
3 weeks is laughable. It takes a few days to get a project properly configured with linting, CI, version control, database on front and back. 3 weeks is the reason that innovative projects usually die on the vine at established companies. PM's and bean counters never want to spend more than a few weeks on a "sprint task" that might not work out. The exact opposite of the mindset you want in a startup |
|
|
It took us 3 weeks in total from inception, prototyping, to setting up a full project like you said (linting, CI CD, AWS containers, database).
To be more accurate, the breakdown is more like this:
• 5 days of discussing, investigating the problem, and design thinking. We took our sweet time here :p
• 2 days of creating a prototype (in the article I mentioned a weekend, using Firebase and React)
• 5 days of reiterating prototype and design within a closed group of testers (family and friends)
• 5 days of MVP design (landing page, branding, etc) and proper project and infra set up (migrating to AWS, database, CI CD, staging and production environments, etc).
So that's about 3 weeks (minus two weekends).
Hope that made sense!