Reading your posts, you seem to have no clue about how programmers work at a professional level, especial senior ones.
Whilst programming, mentally the programming language is but a layer on top of a logic structure for the program and you don’t structure a program from the language up but rather down from what you want to achieve breaking rhe problem into parts and eventually writti g it down into whatever language you’re working in.
It is stupidly easy to learn a programming language (I know at least 20) because the structuring of program blocks (loops,variable assignments, operations, method calls) is the usually the same, plus even the syntaxes of the languages themselves are often quite similar because they’re driven by by similar needs, and even the being intimatelly familiar with the language itself takes at most 2 years.
What takes longer is to be intimiatelly familiar with programming frameworks (bundled libraries, tools and pre-existing high level program structures) rather that the actual languages.
As for your example, those still working as programmers (rather than, say, technical architects) making high 6 figures are normally working in big companies with some obscure frameworks that are at end of life - hence it’s hard to find coders that know them - but are essential for the business (there used to be a time whe people programming in the old version of SAP could make tons of money exactly for that reason) or they’re doing high value obscure stuff that goes way beyond programming, such as being a Quant for a Hedge Fund, were the big bucks are for the business domain knowledge (i.e. understanding complex financial instruments such as derivatives) not the programming stuff.
Reading your posts, you seem to have no clue about how programmers work at a professional level, especial senior ones.
Whilst programming, mentally the programming language is but a layer on top of a logic structure for the program and you don’t structure a program from the language up but rather down from what you want to achieve breaking rhe problem into parts and eventually writti g it down into whatever language you’re working in.
It is stupidly easy to learn a programming language (I know at least 20) because the structuring of program blocks (loops,variable assignments, operations, method calls) is the usually the same, plus even the syntaxes of the languages themselves are often quite similar because they’re driven by by similar needs, and even the being intimatelly familiar with the language itself takes at most 2 years.
What takes longer is to be intimiatelly familiar with programming frameworks (bundled libraries, tools and pre-existing high level program structures) rather that the actual languages.
As for your example, those still working as programmers (rather than, say, technical architects) making high 6 figures are normally working in big companies with some obscure frameworks that are at end of life - hence it’s hard to find coders that know them - but are essential for the business (there used to be a time whe people programming in the old version of SAP could make tons of money exactly for that reason) or they’re doing high value obscure stuff that goes way beyond programming, such as being a Quant for a Hedge Fund, were the big bucks are for the business domain knowledge (i.e. understanding complex financial instruments such as derivatives) not the programming stuff.