One thing I'd like to highlight is learn why behind the things as that will help you understand the choices you made.
For backend try to learn the general approach of a feature. For example, changing password ? User should be authenticated, use current password then , maybe confirm the new password and save to database .
Even more general will be understanding the flow, request , get input , validate , create model if not exist and then save to database.
Because once you know that you have to validate , finding out how to validate would be simple in any language or framework.
As you grow, you will find more complicated stuff like
notifications (polling vs push)
events (pub-sub vs message broker)
I understand your feelings towards backend , I am kind of doing the reverse were I started with backend but now trying to improve my frontend skills.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One thing I'd like to highlight is learn why behind the things as that will help you understand the choices you made.
For backend try to learn the general approach of a feature. For example, changing password ? User should be authenticated, use current password then , maybe confirm the new password and save to database .
Even more general will be understanding the flow, request , get input , validate , create model if not exist and then save to database.
Because once you know that you have to validate , finding out how to validate would be simple in any language or framework.
As you grow, you will find more complicated stuff like
I understand your feelings towards backend , I am kind of doing the reverse were I started with backend but now trying to improve my frontend skills.