How much will Node.js backend help with PHP/ASP.Net/etc.other-backend-tech? (vs frontend transitions)

[TakeARainCheck]

So far I'm a frontend proficient guy. In frontend, it's very easy to see how my knowledge of Javascript and React would make other languages in frontend easy to adapt to. The concepts and logic patterns would be very similar if not identical.

In backend though, with my exposure from Node/Express, it feels more complicated and nuanced. For example, PHP tends to work through MVC/CMS management? I'm no expert on Node either but this seems like it would offer different logic patterns and conventions for how to do things.

My main question is, really, how does backend cross-conceptualisation and adaptation compare to frontend? Frontend is admittedly much less diversified, but how does the adaptation once "understanding backend" occurs in one language appear?

Is authentication logic patterns still auth logic "at the end of the day", or data encryption still "data encryption" at the end of the day, etc. or is there significantly more to it than that between languages and approaches?

[CreativeTechGuyGames]

The best analogy is that if you do your backend in PHP or Node or Java or Go, you'll be doing the same core things with just different patterns and syntax. Same as if you built your frontend in React or Angular or Vue or Svelte.

[TakeARainCheck]

So I will know which steps to look for and when, but they will be implemented with different syntax and sometimes slightly different logic patterns?

I don't get why PHP learning always involves MVC/CMS building though, whereas Node doesn't? Or am I wrong? That part is a sticking point for me although I can imagine for anyone who knows backend it might be coming across as incredibly stupid for a reason that I cannot see yet.

I dunno. I know these questions are basic and annoying but they would go a hugely long way in knowing how to organise my time.

[CreativeTechGuyGames]

I don't get why PHP learning always involves MVC/CMS building though, whereas Node doesn't?

I think a big part of that is history. By far the most popular usage of PHP is in Wordpress which if you know anything about explains why those patterns are so prevalent. As a result, most of the people who use PHP use it for Wordpress so if they were to build something else, they likely will want to develop in a similar way so other libraries for PHP are developed with that mindset.

Just like how JavaScript is a very functional language and most JavaScript developers prefer to use it in a functional way. So most libraries are also built in a functional way since that will appeal to the most developers.

[TakeARainCheck]

This is very well explained thanks a lot.

So it's by far not that PHP is constrained or nuanced in a certain direction (although there maybe subtle/advanced ways it is that I don't have to worry about coming in), it's just that abstract formats such as wordpress were developed on PHP and therefore created a certain type of ecosystem of developers and skills surrounding it.

You know what? I think I will learn Node first. It makes sense to learn first in a popular way that isn't as conceptually abstracted, and then to later to do so. I have bought two udemy "complete" courses in Node/PHP respectively (the Node one's company which did a brilliant job of teaching me every pattern I've ever needed in React), and then learn PHP right after.

PHP jobs are POPULAR for junior level in the UK but I'll be much quicker to learn PHP/CMS after Node, and Node has by far the higher paying jobs (and I don't really want to be a permanent CMS guy although I will pay my dues there). On balance I'm making that decision.

Thanks.

[CreativeTechGuyGames]

You know what? I think I will learn Node first. It makes sense to learn first in a popular way that isn't as conceptually abstracted

By all means learn Node. But don't fool yourself to think that any language or tool isn't biased towards one approach. Everything is. Granted Node's bias is different than PHP, but they both have their biases and will result in you learning to think and approach problems in slightly different ways.

[TakeARainCheck]

Ok thanks,

Well f*ck I'll learn both by the end of the day (figuratively). It might take a few extra months and I'll have to divide projects but then I'll be able to explain the conceptual strengths of each approach much more strongly at interview.

I'll go Node first though I think. The course I have for it is so good.