(I am not saying to avoid talking to people if you don't recognize the company.)
Some blame the layoffs.
I don't think so.
Before GPT, it was a struggle for devs to appear articulate in the domains that they reference on their resume.
Possessing exceptional writing abilities was a definitive competitive advantage.
It's no longer. Now everyone can sound like an expert and craft a pretty good, customized, concise cover letter.
The whole process needs to move to video-based cover letters. It's as simple as that.
Zero content coming from LLM's sounds like this and yes I've read quite a bit of output from a variety of them (including whatever version/release the reply is going to ask).
There's this idea that LLM content is subversively good enough to pass muster, but ultimately if there's more than 3 sentences, it's not and you can ask any content moderator (Like publishing companies).
The problem with using chatgpt today (aside from misrepresenting yourself if you don't state that you are using it) is that it doesn't match your own tone, cadence or patter. When you switch between answering for yourself and using chatgpt 's answer, it is blindingly apparent.
I'm extremely skeptical that convincingly creating a double to fabricate an entire interview conversation will come anytime soon.
When he woke up the next morning, there were 2500 applications. Only 8 of them were from Canada, 95%+ were from India. Maybe 1/4 attached cover letters, every single one immediately recognizable as the soft, impersonal ChatGPT default temperature type tone. They all still checked the “I am a Canadian resident and eligible to work in Canada” box - my understanding is that this is being treated a bit like the “I have 10+ years of Ruby experience” box.
I think that online applications are going to be broken for a while now, especially for junior roles. Any listing which is open will become a honeypot for eager applicants from around the world, hoping their profile will be exceptional enough that the company might turn a blind eye to the visa question.
Either way, I encourage everyone I know to just leverage their network and seek referrals. Firing resumes into LinkedIn seems like a fools errand at this point.
(also by giving enough low level toys to stay interested)
I'm a senior developer at least in years, even writing my first Rails application when it was at version 0.6. I had to look this one up. And it seems the internet doesn't even share a consensus of what it means. Attempts to define it are all over the place.
The non-tech definition seems to relate to tech most as to what people usually refer to as interfaces. In fact, one definition for "polymorphism" that I came across – which I dare say was the most reasonable of the bunch – asserted that interfaces are a formalization of polymorphism. I assume this matches your expectations.
Given that, when would using the word "polymorphism" ever be useful as a senior developer? In Rails land, if you truly needed to communicate the concept to other developers (which is dubious), you're probably going to speak to duck typing instead. That is far more practical.
[0]https://guides.rubyonrails.org/association_basics.html#polym...
Maybe the whole industry has gone that way... but the smaller talent pool makes it a lot more obvious.
Were it up to me, we would be using something else where I work, and not just because of the smaller talent pool (although that's probably the biggest reason). Many of the "delightful" and time saving things about rails either turn out to have relatively insignificant impacts for complex applications, or turn into sharp edges that slow us down.