How to make a web service and not drown in the process?

Question

Software design

There is an idea of ​​a web service, quite complicated (for me).
How to start creating it?
Just take it and start writing code - you start to drown in it, get confused. Everything in the head does not fit, it is necessary to somehow organize this process.
Who does what? What software is being used? How is it customary to take on such projects, organize the development process? You can post links.
I will be grateful.
UPD:
Many agreed that it is necessary to concentrate forces on MVP, i.e. some one main feature. Then the question is: should the database schema be worked out only within the framework of this feature or the whole thing? If the former, will generic problems appear in the circuit due to the fact that I simply did not take into account further development? if the second - you can drown. Or I don't understand something.

Answer 1

1. Select one main function of the service
2. Make it, make it up and roll it out, it will be an MVP
3. Don’t bother with layout
4. Don’t bother with authorization methods
5. Don’t think about the load, don’t optimize the code and database
6. If you caught yourself on the thought of what you think what pattern you apply here in F, just write code that works !!
7. Do not combine writing a service that you REALLY want to run with learning something new (language, database). Drown in your studies and never run out.
This is all from my own experience of writing a project, I tell you and not unfounded))

Answer 2

Use the MVP approach - just don't confuse it with the model view present
Link: https://en.wikipedia.org/wiki/Minimum
viable product,
MVP at the same time, it performs the function you intended. A lot of startups took off this way. The advantage is that you do not spend a lot of effort on its development, but do only the most necessary (the bare minimum for it to work).
Organize work in something like Trello
And of course, try to involve as many people as possible in the development who really do something all the time, and not just look and leave, there is GitHub for this, for each even the smallest feature no more than one branch should be done in the git, otherwise a professional will drown even with 20 summer experience.

Answer 3

It is noteworthy that the "sit and work" option is not even considered.

Answer 4

First pump your head on simpler projects.

Answer 5

First you need to design the entire project and only then start writing.
1. You paint all the urls and write what data will come to this url and what will leave.
2. You design a database.
3. Write code.
Read something on the topic of the software life cycle, it explains how to write big projects.

Answer 6

Treat your job like a business.
1. Write yourself a technical specification as if you want to order a product.
2. Look at the TOR and evaluate the cost of work based on your rates
3. Think about whether the investment of your time will pay off and what risks
4. Think about how to simplify the work
...
99. Start writing code according to your TOR

Answer 7

First you go to the library..
htmlbook.ru
php.net
etc..
And then do what you want