I’m not the only one “fighting hard to make the distinction”. Technically the distinction isn’t minor. One runs only on Windows, is in maintenance mode according to Microsoft and won’t get any major updates going forward and one is cross platform, actively being improved upon, and is the future of Microsoft’s development platform according to Microsoft
And you’re in Europe, do you really have an on the ground pulse of what most Fortune 500 American companies are doing? I’m frequently looking at the job boards and most greenfield projects are (unfortunately it’s my favorite language) not focused on C#/.Net at all and those that are trying to get from under both Windows licensing and the increased resources requirements and are moving toward .Net Core.
There are still holdouts for VB6 and I still see jobs wanting people to maintain them. But would you say maintaining legacy VB6 code was a good career move?
Until the company decides to change directions, you suffer from salary compression and inversions because HR decides to pay new employees market rate and (the hypothetical) you only get cost of living raises.
The last thing I want is to be tied to a company because I am not competitive in the market and then start complaining about “ageism”
And I’m on the opposite side of the country from the west coast FAANG and startup culture. I’m the definition of a standard “enterprise developer”.
And you’re in Europe, do you really have an on the ground pulse of what most Fortune 500 American companies are doing? I’m frequently looking at the job boards and most greenfield projects are (unfortunately it’s my favorite language) not focused on C#/.Net at all and those that are trying to get from under both Windows licensing and the increased resources requirements and are moving toward .Net Core.
There are still holdouts for VB6 and I still see jobs wanting people to maintain them. But would you say maintaining legacy VB6 code was a good career move?