Me too, however this is another case of exchanging IDE for text editor without understanding what is being lost, or never having used the IDE to its full potential in first place, thus not knowing what is being left behind.
I was in a meeting with a colleague about a PR for some python code. One of the things I noticed was that he had an unused module that contained an import of a non-existent class from another module. I know he uses Pycharm, so I mentioned to him that this kind of thing should be hard to miss, because the linter in Pycharm should have marked it, and the folder it's in, as red.
He tells me, and I quote, "Oh, all the files are red."
This was the third wtf in that same meeting, so I think I did ok waiting to lose my cool until then.
Second wtf you may ask? In the goal of changing the storage of our data, he implemented 3 of ~10 behaviors of the existing library, and silently ignore all calls to the remaining 7. Guess which 3 were never used in the existing library!? :D
20 years "experience". Total incompetence. I should correct that: 17 years. After he was hired, during our first lunch together, he admitted he did nothing the last 3 of his previous employment, getting stuck in some org void where he just kept quiet and sat at his desk every day.
Cowabunga. I do totally believe you, though. I was the guy doing fizzbuzz screens at a prior job. Before that, I would not have believed the failure rate for that step of the process. "The person has a job as a senior software engineer? Of course they'll ace fizzbuzz! It's insulting to even suggest otherwise!" And yet. I bet at least a third of the candidates simply could not pass that to save their lives. I went out of my way to be the friendly, relaxed, conversational interviewer, too. I never wanted to turn away a good candidate because I intimidated them or made them feel uncomfortable. And with all that, it still didn't work out.
A concrete example: one person could not get it through their head that they could write a function to return the correct value, then unit test that function with arbitrary known values. My question: "how do you know if it gets the right answer for 1,000,000,000,005?" What I wanted:
There was a binary search problem that I gave in my interviews, in the context of test and measurement. So, instead of reading a value of the monotonic curve at some index in an array, you would have to set a power supply to some voltage (independent) then read the resulting value from a volt meter (dependent). So, exact same concept, different way to "index" and retrieve the value.
To help my explanation, I had a plot to show an example monotonic y=x^2 as a blue line and an example target value as a horizontal dotted red line.
One guy I had said something like, "You can start at the left of the image, then go down looking for a blue pixel. If the blue pixel is at the red line, you have found your value".
So, he wanted to search the image of the plot rather than the data behind the plot. I tried to get him to understand that was an example, and that we had the data, and that he would have to do the measurements himself, but it just resulted in a short interview.
I eventually told all the hiring managers that I could help interview again after their screening process was fixed, at which point I learned that they just removed software from the screening process to save time. This was a ~50% software position.
> or never having used the IDE to its full potential in first place
As more and more people delegate stupid things to their agent, this type of person will become increasingly common. Products like RustRover and CLion will be a much harder sell to audiences that don't even use an LSP in their day-to-day workflow.
JetBrains is probably working on a contingency plan as we speak.
