He'll get out - maybe through the embassy. It's not like there would be extradition between Russia and France with the relationship as it is at the moment.
He's not persona non grata. He visited Russia last time in October 2021 (see recent reporting by Vaznye Istorii).
(I doubt he'll escape to Russia though).
Agreed. You say you're not depressed but actually when your describe how you feel it sounds a lot like depression. It might be a good idea to talk to a doctor about it.
In my country, last year it was definitely a candidate's market: I had recruiters reaching out all the time and I got the first job I applied for. This month I've been applying for jobs and not getting interviews.
From the conversations I've had it seems recruiters want someone who has an exact skill match for the job. They don't care what else you have done or how many years you have under your belt it's gotta be the exact list the employer wants.
I'm now optimising my resume (CV) for the job. I summarise the stuff that I think recruiters / employers don't care about.
The other thing I've noticed now is that when a recruiter reaches out quite often that role is not listed publicly anywhere. So your profile on the job systems - linkedin and elsewhere - better look real good or you won't get a call.
I've helped hire three different developers where I work now, and been a part of countless interviews. I've found it much more beneficial to look for people who think like programmers than know any given language. Unless you're talking really specific, deep stuff in a given language, the syntax and whatnot are trainable. What you can't really train people to do is take a large task that we want our software to accomplish, and break that up into pieces or steps that can be built. Nor can you teach the basic pragmatic techniques that go into things like using objects and classes.
We hired on someone who had barely touched Swift as he'd been out of the iOS environment for many a year, and even before that had never done a ton of app development, but he had solid fundamentals in other languages so I went to bat for him and got him hired. Not even 4 months later he's a top contributor on our team.
Spot on. Even too many developers think that their main skill is recall of language/platform/tool specific niche arcana, and while it's true that sometimes having that will reduce friction, it's rarely what actually drives things forward.
Arcana are concrete and relatively easy to test for, though, so my theory is that it's a bit like the story of looking for the keys by the lamppost because that's where the light is, even if you dropped them somewhere else.
(Didn't see this reply and it's an interesting question so excuse some necro)
For my case above, this devs experience with iOS was so minimal he didn't even have it on his resume, he listed himself solely as an Android developer (but like most places we develop for both, so it was useful experience regardless). I have a strong feeling most HN folks would absolutely interview like I do, but the problem is the interview is the last step of an otherwise highly bureaucratic process that is more or less entirely devoid of technically-minded people. Like, even the recruiter that got me my job many years ago, bless em I love where I work, but even that recruiter didn't know shit. They found me because I specialized in a lot of the things my employer was after, and that sounds alright, but that was solely based on the keywords: Swift, Objective-C, etc. A recruiter, for example, won't understand that someone fluent in Objective-C, while they're going to have an adjustment period, could probably competently write C, C#, or C++ as well with some help and training.
If the internet is to be believed the average software engineer changes jobs every couple of years.
If that's true it makes some sense for a company to want to only hire people whose skills exactly match the specific thing they are hiring them to work on. If they only think the new hire is not going to be around long term why put resources into teaching them new skills?
Oh hey, I've heard this joke before -one manager says to another "But what if they leave after we train them?"
The other manager asks back "What if we don't train them, and they stay?"
Not investing in people (and jobs) is a two-way street; there's always someone young and naive to think hard work and investment will be rewarded, and most companies have been around long enough to have set the assumption that "No it fucking doesn't".
The new guys need the most investment. Companies hiring are actively teaching them to be jaded by not investing in their employees.
that's a chicken and egg problem. People change jobs frequently mostly due to two reasons:
1. higher pay
2. to get away from bad management or a bad work environment (same thing really)
If it's the kind of place that doesn't help train new skills, that falls under "bad management". Employees could collectively try to be the better person first in fixing this, but most modern history would show that most employers if given an inch will take a mile, and will generally pay the least amount possible, expect one-sided loyalty, and overall get away with everything they can until either regulation or market forces force them to change.
>it makes some sense for a company to want to only hire people whose skills exactly match the specific thing they are hiring them to work on
The good ol' "10 years of experience in Swift" approach... Though that joke is so old now that it probably is possible to legitimately have that.
That approach would make sense if the requirements seemed possible to begin with. And the salary was enough to attract that kind of niche talent. You're basically asking for a consultant for an employee's salary at that point.
I live in a country where roundabouts are common. They're great for relatively low traffic intersections as you can often get through much faster than lights.
They are a liability when traffic levels are high enough - say during peak times - when one inbound direction is blocked by another.
I don’t think Americans loathe roundabouts. They’re just unfamiliar. So when someone says “would you like to add an unfamiliar section of road design in our town?” most say no.
> They are a liability when traffic levels are high enough - say during peak times - when one inbound direction is blocked by another.
The rule should be that when traffic is bumper to bumper, the "zip" is made mandatory. That rule already supersedes the normal rule on, say, many (all?) european highways when the highway goes from, say, 3 lanes to 2 lanes and in case that creates a traffic jam: people in "their" lane doesn't have the right of way anymore. It's one car from one lane, one car from another lane: the "zip".
People in a roundabout should lose their right of way when traffic is bumper to bumper.
Where I live people are extremely polite on the road so I don't even know if the zip it's mandatory: people shall simply act that way.
In countries where road rage is common and people misbehave, like France, just make it mandatory by law.
The zip does nothing on the roundabout.
bumper to bumper is very-rare, and it mostly happens momentarily due to pedestrian crossings placed directly after the entrance/exit of the roundabout.
What is actually super dangerous are the non-standard 2/3 lane roundabouts where the first lane gets "ejected" at the next/second exit forcibly, while the 2nd lane can either exit or continue on the roundabout, so many lorries in the 1st lane try to runover those in the 2nd lane trying to exit.
I'm in France and we do Zip in my area (which is quite touristic and see huge traffic right now, so I do that quite often when I drive in summer). But it is true that around Paris and in southeast France, people usually misbehave and act like entitled pricks.
This is another one of those "I used this for 5 minutes and found this out" naive posts which add nothing useful.
Check out the host LLM's at home crowd. One app to look at is llama.cpp. Model compression is one of the first techniques to successfully run models on low capacity hardware.
There's an easy fix for AI transforming the output of the Internet giants into useful content for us: just block those AI apps/services. They are determined to be the interface between humans and machines because that is where you make your money.
Silicon Valley is not the only place to find engineers who know what they're doing. Some of us want to stay in our home country and/or don't want to jump through the hoops that American tech companies demand.
