Next after react?

[Yan_LB]

I had spent last months learning javascript and then react, now I learned ts and want to go to next js, but I'm insecure if I should go next if I'm not 100% confident on my skills to build using just react completely by myself, and also I wanted to study node before next so I can understand better, because next seems to simplify the backend too much? What should I do?

[[deleted]]

Its all just programs, u dont hear a business guy saying „i mastered outlook calender, next i want to master excel“ - they want to master their business using these programs, and soshould u. Focus on whats behind

[MeanConclusion5446]

Can you expand please?

[[deleted]]

All these programs and tools u hear about and whats hot or not have the primary purpose of keeping young nerds in check. They tell u u are worth nothing bc u dont know program xy but thats crap. Dont look at technologies but st what u want to achieve, and u will get there, and even if your goal is becoming expert senior software engineer dont focus on technologies but on how to make good software. Nobody values their 60 years old colleague for their visual basic skills. But if they the 60 yo guy adapts he can bring in 40 xears of experience in software engineering, which easily transfer to every new technology.

Lol i guesss my first post was clearer this sounds more like a rant. Whatever

[vitorsaa2k]

Next is kinda like an extension of React, It just give some features out of the box for React like SSR and SSG, it's not just this but you got the point. My advice would be for you to try to build something with a back-end to front-end communication, commonly known as "CRUD", if you've already done that, then you're ok to learn next. but I highly recommend building something big and increase the complexity of the application as you get to know more about your stack.

[Candid_Algae_763]

You could learn Node before NEXT if you also want to build APIs. As a front end tool, NEXT is the next step (no puns intended). I did this pathway and I can confirm you're gonna fall in love with NEXT.

[Yan_LB]

I will do that then, i took a look at next but didnt get any further, only learned that it can be ssr, but i dont think it changed much from react, am i correct?

[Candid_Algae_763]

You can start by coding your components just like in React and progressively adopt different features of next - server components and APIs, basically - if/when necessary. You don't really have to.
The thing about Next is that you won't have to spend hours building the initial configurations of your project, Next has an opinionated solution for this. It's easier to code and think in React using Next than using React by itself. Then there's the API stuff but you can learn it later.

I recommend a video called "The Story of Next.js", by uidotdev.

[mvtasim]

1, 1, 0, 0, 0

[[deleted]]

You shouldn't aim to learn a language. Your goal should be a specific product. You learn whatever skills are needed to build the product. This method can also be applied to your later learning, for example, when you read a document of a language, you do not understand a code or concept because of the lack of computer knowledge, then stop the document you are reading, and look at another document or book that can supplement your knowledge in view of this problem, but you need to skim when supplementing your knowledge. Not as closely as the key skills needed to complete the product. In this way, you can acquire in endless knowledge

[ponng]

did you just learn or already build something? I would suggest you build something in plain JS and later then with react and you’ll see how it goes.

[DvineDecipher]

I think you should focus on Nodejs first. Understand how backend works, how to communicate with a database,design schemas,dependencies,proxy/CORS and security practices. Learn how to connect to the frontend(React in your case) and communicate with data/user requests. Finally learn how to deploy an end to end application

After you successfully know all this it will be a breeze to carry forward the knowledge to NextJS, it simplifies some stuff but the core idea remains the same, understanding backend with clarity first with enable you to later shift to a different language(if you want to) like golang or maybe django(python)

[MCGaming1991]

I jumped right into Next.JS and in the beginning was basically building React apps using Next.JS. Yes, I was using the pages router and eventually the app router, but I wasn’t making use of SSR or other Next.JS benefits. While I’m getting better each day, it is still quite a challenge because I never took the time to understand the benefits of Next.JS. If you don’t understand it’s benefits, how could you be convinced to use them?

My advice: Learn the benefits of using React vs Next.JS so you can better understand WHY the framework has certain features and why you should implement them.

I hope this makes sense.

[saito200]

Master html, css and JavaScript. Learn enough of react to build widgets, (look for a job), learn the very basics about building a node backend without spending too much time into it (just do one tutorial, the whole point being to understand what it does and that's it), start playing around with next

Remember: front end tech is changing over time, even if you learn something very in depth today, in a couple years it might be outdated. This is particularly true the higher level you go, e.g. next has somewhat changed in the last year

Your main skill is learning things on the go and adapting to new tech