Try porting a very small bit of behavior into a new tiny library or module that is Typescript based and independently published. Enable the strictness checks in tsconfig - really, really resist the urge to use any, and enforce that any is disallowed in tsconfig. Familiarize yourself with its utility types that really trip new authors up. "Record" comes to mind here, and others that involve generics if you haven't before worked with generics. Some of the type error messaging can be pretty obtuse - don't be afraid to paste them into an LLM (or use Copilot enhanced Intellisense) to explain what it actually means. IMO the type violation messaging is a weak dev experience point for new authors, so don't sweat it if you occasionally "struggle to make the squiggles go away".
This is why I will never touch Javascript again. Long ago when I worked on web stuff, half my workflow was spent in the debugger tracing garbage to find where a typo was. The industry moved to Typescript, and now assuming the strictness checks are enabled, if some Typescript transpiles successfully, I can be 95% sure whatever fuckup I observe at runtime is a logic problem.
Weakly typed languages were an awful idea. But in general, if the compiler isn't able to detect most runtime issues (like with C++ here), it's not going to be the most productive language to use for building solutions compared to smarter alternatives.
Surprising, considering arcade game clones are already in github. These models apparently cannot be trusted to even copy and paste a fully working project if that's basically what you're asking for.
I agree, but for a different reason. Demand for senior/principal engineers is still present, especially for those "third party vendors" you mentioned. But companies are not interested in hiring and training junior devs. They'd rather outsource when long term quality and tight control is not important. Or, for the bigger companies, they'll hire H1-B instead. There are enough senior engineers to be shuffled around for many years now that engineers have reached saturation in many markets.
And it's not that all the software that needs to be created is now present and "good enough". For some industries, that might be valid, but it is definitely not universal. The thing that IS universal is that experienced engineers have become far more productive than they were a decade or two ago because of the large software ecosystem available now. That productivity might outpace what some companies actually can make use of to directly improve revenue or margins compared to their current headcount. (Engineers might still be busy today, but not on things the company considers very valuable.)
I wonder if we will see growth in software consulting or dev agencies as smaller companies find they can do more with less, and only occasionally need more firepower without fully outsourcing.
You don't need a teleporter. You just need a plane ticket. Living in many countries (illegally) is as easy as flying in and not flying back. For many, you don't even need a visa if you pretend you're only there for a short stay.
The only non violent thing that puts those kinds of people in their place is to be humiliated somehow. But you have to remember, the things they feel are extremely embarrassing are different than what regular people find embarrassing.
Things that make them seem weak, insecure, vulnerable, etc are what you have to highlight. Having extramarital affairs? Avoiding taxes? Manipulating share prices? Nah, they feel strong when they do those. Their followers see them as a strongman who does what he wants. But this guy is actually 5'2"? This guy shit himself in public? This guy threw a terrible opening pitch at a baseball game? That's what makes their followers lose interest. You have to consider what would make their followers think of the strongman as a weak loser.
Well assuming you're not "financially successful" and talking about wealth classes that make their money from working, then by comparison they don't do anything differently when their paycheck arrives, or even know what day exactly they get their paycheck. If someone is living above their means or otherwise financially at risk, they're paying close attention to the numbers in their accounts. More subtly, they might say something like "I just got paid, let's go out for dinner" or "I'll buy those tickets on Tuesday" when there's no reason they shouldn't just get them now for whatever it is.
Try porting a very small bit of behavior into a new tiny library or module that is Typescript based and independently published. Enable the strictness checks in tsconfig - really, really resist the urge to use any, and enforce that any is disallowed in tsconfig. Familiarize yourself with its utility types that really trip new authors up. "Record" comes to mind here, and others that involve generics if you haven't before worked with generics. Some of the type error messaging can be pretty obtuse - don't be afraid to paste them into an LLM (or use Copilot enhanced Intellisense) to explain what it actually means. IMO the type violation messaging is a weak dev experience point for new authors, so don't sweat it if you occasionally "struggle to make the squiggles go away".