For further actions, you may consider blocking this person and/or reporting abuse
Read next
Top Image Editing APIs 2024
Sohail Pathan -
Why the stern Guardiola shouted at superstar Foden?
Safetotosite pro -
'This is GOAT class' Messi's 2-goal, 1-assist one-man show as Miami takes MLS lead
Safetotosite pro -
"Charney joins Arsenal GK in tears" Wolverhampton nucleus of chain transfer
Safetotosite pro -
Top comments (3)
I do not know what you background is, but server side coding, to me, is a lot easier than the frontend one. No need to accomodate a lot of different browsers and no interaction with users (you get all the data you need to elaborate along with the request).
It is a different matter if you intended to learn to use a web framework. Everyone has a somewhat unique vision on how a request should be served and on how to interact with other backend components and servers. Key concepts are quite same but implemented differently.
Something tells me that you're not alone here. 😅
You got this!!
I'm also in the process of learning the server-side of things. I started with a Django tutorial (only ever used Javascript until that point), so it was hard to get complex concepts, like requests and responses, models and databases, rendering with templates mentor thought it would be good for some reason.
Once I started on NodeJS (my main focus, for JS reasons lol), I was surprised at how much of those complex concepts I had absorbed from my experience with Django, making it much easier to dive into the syntax, the architecture of a node application, working with Postman, and the libraries. Also, while reviewing the concepts other than learning them for the first time. So I guess the Django exercise had its reason.