How to get started?

This is just what I personally tend to do (assuming the idea has legs):

Start a trello board to keep track of ideas and what I'm currently working on.
Sketch out what the pages should roughly look like on paper.
Then I just start coding it... usually getting the "users" boilerplate under control first, since almost everything will need to be keyed off users. i.e. user signup/login/reset password etc.
I tend to do the frontend, backend for a particular slice of functionality all at once, it's slow going at first, but it makes it faster to build other features later on.
Payments and other third party integrations I usually save for last.

I recommend picking a "boring" tech stack, full of well proven technology and not the latest flavour of the month (i.e. react).
Examples of boring tech: django/rails, nginx, plain old server rendered html pages.

Say something nice to sosa067…

1
This is just what I personally tend to do (assuming the idea has legs):
1. Start a trello board to keep track of ideas and what I'm currently working on.
2. Sketch out what the pages should roughly look like on paper.
3. Then I just start coding it... usually getting the "users" boilerplate under control first, since almost everything will need to be keyed off users. i.e. user signup/login/reset password etc.
4. I tend to do the frontend, backend for a particular slice of functionality all at once, it's slow going at first, but it makes it faster to build other features later on.
5. Payments and other third party integrations I usually save for last.
I recommend picking a "boring" tech stack, full of well proven technology and not the latest flavour of the month (i.e. react).
Examples of boring tech: django/rails, nginx, plain old server rendered html pages.
monsiv

·
7 years ago
·