w.cd had the best recommendation system for music and audio equipment. The communities that tried to take it's place after don't come close.
It's a shame because I don't know where to talk about it anymore. r doesn't come close, at least not yet. The community music collages on w.cd were unreal.
Or more recently, if Bill Gates doesn't get the will of the voters he will spend millions and millions of dollars circumventing state supreme court rulings based off of legal technicalities because you believe that you are right and people are wrong.
Not too mention, at least in America, the vast majority of American lives are far worst off than they were in the 70s, 80s, or 90s. Making smart phones and personal computers just made rich people richer.
When I interview candidates who mention github contributions or courses they've created/taught or talks they've given I never have time to look at it. I'm literally told we're bringing someone on site maybe a day or two in advance, mostly it's day of. I don't have much time to personally comb over their resume sadly.
If you can bring this up during the interview I'd greatly appreciate it otherwise don't assume these things (open source contributions, blog posts, talks) will help you get interviews. What they may give you is the ability to network with people who are hiring which gets you an onsite.
I've work for large national ISP where they are heavily trying to create a new series of network engineering tools (device discovery, adding new ARs with ease, upgrading existing devices, pragmatically change thru-puts between regions based on load, etc).
Most of the backends for these types of tools would explicitly be done in Java. Why did they chose Java? Mostly because they would staff entire teams with H1Bs and dump them after 5 years. The directors of these projects would only hear about "buzzwords" surrounding the latest tech if they themselves went to conferences or happened to luck out if the project managers they hired had varied experience.
Oddly enough, there's a lot of greenfield work being done using Scala at Verizon and Comcast. But from my direct experience, it's entirely dependent on the team. The more the team doesn't rely on contractors the more likely they are to use niche tech.
I forgot the shinning examples of conservative rule that is Alabama and Mississippi. For all the faults that California has political, it's still an economic powerhouse.
This is going to be an extremely cynical take but most software jobs (>80%) are basically the same. That goes for the companies as well, we aren't as unique as we think; and the companies that are unique or doing unique work aren't exactly having trouble finding employees (FAANG vs nearly everyone else).
If you want an employment as a beginner apply to as many postings as possible. Only do research for companies once they want to talk to you, anything else is a waste of time. It also takes very little time filling out job applications (outside of obnoxious companies that ask lots of behavior Q), it should less than 10 minutes to fill out job apps.
IDK how to feel about cover letters, every company I've worked at (startups, national ISP, to massive insurance companies) have stated they never read cover letters sent. They just want to make sure candidates have all the keywords on their resume before even talking (this part is largely automated away).
I have a basic cover letter that explains what I'm doing at my current job and how I'd like to work at $company doing $unique_stuff. Basically my cover letter is 90% the same between job apps, but I change the intro paragraph to match the title, company, and job description.
But as a beginner or moving to a new city where you know no one, apply to everything everywhere. It's a numbers game and even as you progress in your career, you may not command enough talent to target specific companies.
Before changing jobs, I was in a WeWork location at DTX in Boston. There were many rooms that were empty, but Puma was paying for an entire floor so maybe they were making the difference up with large corporation clients?
My current org is composed of mostly MS and PHDs (I'd honestly say 60% have graduate degrees), the only thing it convinced me of is that if you're working in my company and went to MIT (or any other good school) something is wrong with you or you're a foreigner who took whatever job was willing to sponsor your green card.
Why shouldn't doctors and the medical industry take the blame in the US? They artificially limit the supply of Doctors in the US and have the audacity to claim that building more medical schools will ruin their already lucrative careers.
Are there any resources or articles you'd recommend to get a more in-depth view of CSS? I'm a frontend developer but I always struggle with CSS beyond the basics.
Understanding how you you created this is very enlightening.
It's not really excuses when the person doesn't understand what they are doing or why. The problem is entirely with how NPM downloads dependencies, not exactly typescript.
The OP is rightfully getting type errors due to conflicting type defs, why is that a bad thing?
It's a shame because I don't know where to talk about it anymore. r doesn't come close, at least not yet. The community music collages on w.cd were unreal.