One thing I learned from consulting is if you position yourself as the "fix your mess" guy you have to be very defensive. Ask for more up-front, and bail at the first sign of underpayment.
Be pleasantly surprised when a poorly run project is being run by nice, honest people. Prep for the opposite.
According to levels the pay band caps out around $250k and a principal title. It's good but probably not enough for most to put up with the culture long term.
Short ETFs are usually leveraged and make for a really good way to lose money.
Realistically, timing is the issue. "This is a bubble" is worth ~nothing. "This is a bubble and it will pop in late December" is worth a lot if you're correct.
I was going to agree with you until the implication that it's learning the nitty-gritty details that's important.
I can teach someone the details on the job. Give me a new grad with strong fundamentals, a love of programming, and an interest in the domain and I'll teach them in sixth months whatever they missed in college that's relevant to the job.
However I've noticed that the fundamentals are so watered down, even at top-tier schools, that young devs like that are harder and harder to find.
There are externalities with this approach. A big issue with clothing donations, for example, is they put local textile manufacturers out of business. Why buy locally made whatever when you can get second-hand name-brand clothing for cheap?
How is that not a problem with GDPR? They passed a law which relies on technology which does not exist. There is no way to safely and reliably identify an individual electronically.
I think that's exactly the problem -- small/medium companies can't really afford to hire someone to do GDPR compliance (or at least, do it well). It's textbook regulatory capture.
It's because I've been trying very hard to understand what your contention is. The bits about peacocking and resume-padding are... unconvincing.
> ...improve UX, performance, maintainability, and development cost.
I don't buy it at all. As mentioned, I've done both professionally and there are reasons I keep picking React (or a hybrid ala Next) that don't involve a bigger paycheck or "peacocking".
> Your manager or project owner or whoever says "we want a webapp" are you gonna stick your neck out and argue against it?
The question is: what are you going to argue for instead? Not using the web at all is a non-starter, especially in the retail space where you'd get killed by a web-based competitor.
I don't know what your experience is, but historically my bosses haven't given half of a damn what tech stack I use. They care that I deliver on what I promise. Hypothetically, I could still be using PHP/HTML/jQuery but there are a great many reasons I don't and not one of them has to do with padding my resume.
Be pleasantly surprised when a poorly run project is being run by nice, honest people. Prep for the opposite.