Not difficulty, danger, or years spent studying challenging topics.
Changing a color... that's basic html/css-- that's the lowest pay rung of front end developers, which is the lowest paid occupational field within the occupation of full stack web app engineers. So, you're grossly exaggerating. People who just change colors of a web site might make $15-20/hr in the US.
The folks making $150-$200k+ have skills in frontend development, serverside development, databases, plus often things like data engineering or setting up/maintaining cloud computing infrastructure. From there, add in specialty Security knowledge or Machine Learning or highly efficient massively global scale+speed programs, and you'll begin to understand how they're making $400k-$600k+
For example: Go have a look at kubernetes (combined with Docker, Helm, and a Cloud provider + all the various underlying technologies which involve an OS and 2+ programming languages and/or frameworks) and tell me how difficult it is compared to machining + CNCing + welding a metal part. Not to knock machinists-- I've worked on metal machines and I understand why master mechanics make $100k/year.
But I also see why they don't make $200k/year (exception for luxury vehicles)-- there's only so much to learn and only so many dimensions of complexity, especially in terms of continuing education on new technology.
I've met precious few devs of any flavor who understand databases. Not just "how do I write SQL," but actually understand what the query optimizer is doing, minor but infuriating differences between DB flavors, and critically, troubleshooting them.
ORMs and cloud DB providers have enabled people to charge ahead without understanding the consequences of their actions, and when latency starts climbing, just scale vertically!
Re: Kubernetes, again, managed services and package providers like Helm have made it easy for anyone to spin up a K8s cluster and even successfully run things on it, without having the underlying ability to fix or maintain it when things go awry.
> and tell me how difficult it is compared to machining + CNCing + welding a metal part. Not to knock machinists-- I've worked on metal machines and I understand why master mechanics make $100k/year.
> But I also see why they don't make $200k/year (exception for luxury vehicles)-- there's only so much to learn and only so many dimensions of complexity, especially in terms of continuing education on new technology.
I can simplify k8s down to "this is just a bunch of containers that run small pieces of software that talk to each other and autoscale up and down as you tell it to", and naturally that doesn't scratch the surface of what's going on.
In 4+ DoF metal manufacture, there's so many things to keep mind of. Basically, those people are metallurgical-based materials scientists. They'd be in charge of helping choose the materials for the application, billet sizes from the ingot factories, QA at all levels, impurity calculations from the ingots, grain structure sizes, can even be radioactivity measurements.
And then there's the actual machining process. If you've ever used a 6DoF mill, its nowhere near idiot-proof. And one improperly tightened part = damaged 6DoF head. That's a sad day indeed. And you're not done after the part completes. There's also post-processing all the way on up.
And I didn't even discuss metrology - or the study of measurements. Measuring what you're doing is the difference between a passed part and a failed part. And your failures may be caught upstream. And depending on some parts, you may also be doing xray spectroscopy to determine voids and other subsurface defects with the machining type you used.
You also mentioned welding. That's its own massive area of tons of failure modes, not all which also can be seen by the naked eye. Or, imagine doing underwater welding in a water tower that sprung a leak because someone shot at it. You're going up with 200 lbs of equipment, including SCUBA gear and thermite or a thermic lance.
To be honest, I have it easy. I work remote as systems engineer. I thought about switching to EE if the economy cools. But the "blue collar" (Read: tremendously skilled roles) are looked down on because they mess with physical stuffs. And the EE's do physical but are considered white collar, so they're "more acceptable". But I try to see them as the fellow professionals they truly are. The end of the day, they can hold their stuff and go "I made this". I certainly can't hold up an EC2 and say the same. Doesnt have the same feel.
Not difficulty, danger, or years spent studying challenging topics.
Changing a color... that's basic html/css-- that's the lowest pay rung of front end developers, which is the lowest paid occupational field within the occupation of full stack web app engineers. So, you're grossly exaggerating. People who just change colors of a web site might make $15-20/hr in the US.
The folks making $150-$200k+ have skills in frontend development, serverside development, databases, plus often things like data engineering or setting up/maintaining cloud computing infrastructure. From there, add in specialty Security knowledge or Machine Learning or highly efficient massively global scale+speed programs, and you'll begin to understand how they're making $400k-$600k+
For example: Go have a look at kubernetes (combined with Docker, Helm, and a Cloud provider + all the various underlying technologies which involve an OS and 2+ programming languages and/or frameworks) and tell me how difficult it is compared to machining + CNCing + welding a metal part. Not to knock machinists-- I've worked on metal machines and I understand why master mechanics make $100k/year.
But I also see why they don't make $200k/year (exception for luxury vehicles)-- there's only so much to learn and only so many dimensions of complexity, especially in terms of continuing education on new technology.