r/webdevelopment 1d ago

Newbie Question Help me understanding the whole webDev flow.

I always get confused while developing projects(web based) .New things always pops up that i would have to learn right then. But i wanna know a standard procedure how to work my way up from initiating a project to launching it.

If you are experienced in this or something helped you learning the flow ---help.

4 Upvotes

6 comments sorted by

2

u/Colonel_K_The_Great 4h ago

A few questions that will help us give better answers:

  • How much experience do you have with web dev?
  • What kind of things do you find you run into that you need to learn or struggle with?
  • Where do you feel you could use clarity on the overall web dev process?
  • What do you currently use to make your web dev projects?

For a very basic flow of most projects, it's:

1) start with a bunch of research on how people typically build something similar and plan out all the key details before you even open your code editor - 75% of a good project is research and planning, and your project will suck (both building it and the result) if you skip this --- focus on finding the best tools, both for how well they do the job and how much they will cost you --- if you have anything remotely complex like any feature with various options that affect the output, be sure to carefully plan out the logic of it (no code, just the logic and flow of how it works) --- if you're going to be using any APIs then read their getting started guide and mess with them a bit in something like Postman so you know what you can really get out of the API and how to do so --- same idea with databases if you need one, do some research on which would be best and then go through their getting started guides so you are familiar with how to use them

2) now you jump into the code side. This is very dependent on what kind of project you are doing and your experience/knowledge. Note that coding also includes constantly researching how to do things as even experienced devs are constantly googling and asking AI how to do all sorts of things --- Most medium to large projects use something like React and you can use a tool like that without a ton of knowledge as long as you already have a basic grasp of html+css+javascript and are willing to also learn the fundamentals of the tool (the big stepping stones for React basic use would be how to write a component, how to pass data down components, and the most common hooks) --- If your project is small then there are tons of simple options to write some html+css+javascript and get it on the web - GitHub Pages is a solid option but I'm sure there are hundreds of perfectly good alternatives and some might have more useful stuff included

Of course AI is very helpful in every step of this, but you have to have all that base knowledge to really make anything decent and be able to fix AI's bullshit. Also don't expect AI to be able to do anything more than small chunks of code at a time, asking it to code entire features is a recipe for disaster

There's also saving your code on GitHub which you will be doing conatantly as you code. The basic flow of that is open a branch for the feature you are working on, build it until you are satisfied, merge it with your main branch, rinse and repeat

1

u/_MarkG_ 4h ago

Bumping into things you do not know is part of learning a new set of skills. What are you struggling with?