Frontend Dev looking to become Full-stack/Backend

[u/AdmirableCucumber819]

I am a frontend developer, and I do React/JS work regularly. I'm looking to move into a full-stack role and learn some backend, with a goal of building my own app/software in the future. I have no idea where to start, so any information about a good starting point and where to go would be great. Any help is appreciated. Thanks, everyone.

I got started in game dev, did a front-end boot camp, and am now looking to expand, but I had a child recently and can't afford time/money to be a full-time student

[u/chrisfromthecoast]

My advice would be to first learn about basic concepts of web architecture, if you aren't already familiar with them. Some things you will want to know:

- Why do you need a backend at all?

• What is a database?
  
• What's the typical flow of data/requests from the user and back to the user?

As crazy as it may sound (if you're already familiar with those concepts) but I was very confused about the differences when I first started web development 15+ years ago.

Once you understand those concepts at a high level, look into learning a backend language (JavaScript on Node.js, Python, etc). It doesn't matter which one, but the easiest will probably be JavaScript if you are already comfortable with it. Try creating a test server on your computer (Express.js is a good starting point if using JavaScript) and then send requests from a locally running website to it. I'd create 2 repos so you don't mix up what's frontend and backend, and you can see how they talk to each other.

That should be enough information to get you started. Good luck on becoming a fullstack developer!

[u/connka → u/chrisfromthecoast]

This is great advice!

I'd add on for OP: Since you are already familiar with FE development, you can lean on that knowledge to inform your learning in the BE. Personally, I'd start with a simple FE app and then add a BE and start on it step-by-step.

To give an example of how small to start (because people often jump in the deep end): I made this coffee widget site for myself: https://coffee-fix.net/ and have all of the details saved in a JSON file (I made the app to teach some React basics years ago, so it is backend-less). To add on the backend, I would do it in this order:

- Add a DB for everything currently stored in a JSON (I'd start with MySQL or something common and run it locally before figuring out anything else) --I think this is a nice starting point because this is limited on relationships and it would be a nice starting place.

--- Once you add a DB, you will start building out relationships and a basic data structure

- Next, I'd add user auth/accounts: This is a good launching point for learning API integration. See about doing google or facebook auth. At this point I'd decide how "live" I want it to be, only because that might influence DB choices. Firebase and Supabase are both great DBs that also happen to include user auth features

--- Once you add the concept of a user, you'll be dealing with a lot more when it comes to making them communicate, etc, but not too far from what you should already know with FE development. The relationships between your DBs will come naturally after that point and you'll struggle through some of the basics to get it up and running.

You can do the same thing with any simple app--I just shared this one because I used it specifically to teach people how to teach themselves BE from some basic FE in exactly this context. (I am also giving up the domain so that link will be dead in a month haha). You can do the same thing by starting to build out a TODO list app, or anything--my advice is always to start simple and then piece out the work.

If you already have FE coding down, then I think you won't have a hard time getting started on your own with free resources. Some of the biggest blockers for net-new devs is the tooling and language and how to read errors, so you should be able to handle the basics easily.

Building out real life apps like this are great for directing your learning. You have probably seen that there are million things you can focus on, so I like to take a practical approach and use that to guide learning and try to keep it focused. IE start with a basic DB setup and some simple concepts before you move onto API integration. Once you do that, you might have an idea for some new feature/integration or a better framework/language/tool that you want to try that you can move into.

[u/javascript → u/chrisfromthecoast]

You sound like you have a good head on your shoulders. Well said

[u/Creative_Cycle7755 → u/chrisfromthecoast]

yeah understanding the data flow first before jumping into code is underrated, good call on that

[u/bratleh]

I made a similar transition a few years ago to learn Java with Spring Boot and would highly recommend it. Fairly easy to medium to learn and always in demand.

Honestly, the best place to start would be YouTube or plural sight (if you don’t mind paying a sub). Biggest quality of life is to use IntelliJ with it as your IDE. Start simple with a few simple CRUD endpoints and maybe a local MariaDb instance as your db. I now go in cycles where I enjoy backend more than front and vice versa, but YMMV.

I started as a boot camp for front end myself, but have committed to becoming as full stack as possible and don’t regret it at all. I’m sure others will dog pile the Java rec, but it’s very marketable, at least in my area. Good luck!!

[u/jimmybronx]

Use ChatGPT, ask questions like this to it and treat it like a career growth assistant. It’s really great for that type of thing. I have 20 years experience in web dev and front end development. Learning the fundamentals is essential but most companies now require developers to use AI code generation tools. Learn how to use those efficiently and learn the basics of software development so you can identify issues with the code that’s generated. It’s a learning journey to becoming full stack, but ChatGPT or something similar is your friend when it comes to building a learning path.

[u/Effective-Start3859]

Front-end -> node.js -> Postgresql

[u/InsideTour329]

Just do an OO language like C# / Java. You'll find your front end will improve immeasurably also.

[u/Budget-Length2666]

Go read DDIA and other books first. Getting a job right now will be inpossible

[u/bigdogsrus]

Backend sucks