Enough to suspect the developers of imposture. Learn to better interview
Well hello. I just got off the phone, and I'm bombing. How many do not write on Habr, how to properly interview - it does not get better.
They threw me a proposal - Senior full-stack .NET Developer, remotely, cool project, a lot of money. In the list of requirements, a hell of a lot of unrelated things from the world of .net and js /ts. It looks like they just piled all the things that were baked in 10 minutes - with little understanding of what exactly.
It's troubling, but nothing. Interview, I think, will be a developer - a person with whom I speak the same language. I'll tell you about what I did, discuss approaches to problem solving, problems in .NET, prospects for C #. Let's talk about data structures. I'll tell you why I like the structural typification more than the mnemonic one. If it goes well, I'll even share my idea of fixing - always use structures instead of classes as models. I compare FLUX with MVVM, I will tell you how unreal is the symbiosis of FP and OOP in TypeScript.
In general, I look forward to a good conversation.
I was answered and offered an interview on Skype, for some reason it is necessary with a webcam. My laptop is broken. There were a few minutes, and I decided to run out to the nearest store. There, people apparently understand that webs are not needed by anyone. But what to do - take a doroguschy action camera, pick it from the shell, attach to the cud to the monitor.
When the interview started, I understood why the webcam needed - that I immediately realized which smug place in front of me is sitting - "Yes, I can see from the half-look what you are like."
Send "signor" questions. What is protected internal? I answer. What is ref, what is out. I also know, but I suspect that he does not need detailed answers. What is the difference between dynamic and Object? I feel like at school, but okay, I'm telling. What is virtual?
Kill, I do not remember. I look - the mountain spreads with pride, glows. Arrogance is pouring from the screen. I'm glad that I ate another boob that does not know the "basic" things. Self-affirmed, you can search for the next. The interview, of course, ends.
I close skype and, of course, I immediately remember that for virtual. But the company already, for sure, is sure that I'm 100% profneprigoden.
And it seems to me that what happened is a very unhealthy symptom in the world of developers.
Most recently, there was an article about the fact that when hiring we see only functions. What if the developer did not memorize all the most unnecessary things for memorizing - he is not taken, and it's terrible. But I think the problem here is quite different. Business for some reason is insanely afraid of impostors, but has no idea how to sift them.
And he is so afraid that now he sees them everywhere and inflates the problem to attention, which she does not deserve at all.
Those. these people are seriously working on a scenario that some kind of left-handed dude who has never worked as a developer will come to them as a lord. Really? They are not just fixated on this approach, they put it in the design center of the first interview (more than one interview is a problem in itself, but this is not the case now).
But reducing the risk of hiring impostors, companies are reducing the chance of hiring good developers. Worse, they demoralize good developers.
Now my words to myself that I should not remember virtual, even for me sound like an absurd justification for my own unprofessionality. The money that I have ever been paid for my work is a mistake. I deceived everyone around me. I need to learn the spices of all the technologies that I dared to put in my resume.
And it does not matter that I really try to avoid classical inheritance, preferring composition to it, and I design my classes and systems in such a way that they do not have to make heirs of them. It does not matter that I remember the behavior of virtual and its purpose, I do not remember only the word itself. What I regularly develop using four programming languages, and I can not remember thoroughly all of their dustiest corners.
His stupid skills to write good code, I can stick myself to where I want. The market asks virtual for virtual.
This is very bad. You're afraid of impostors, and I'm afraid of the next one.
But I'm not ready to be a crab. I want to be - and I am - a developer. I'm the guy who takes this business problem of yours, looks at what tools I have, corrects it, decomposes it and displays it on the solution through a competent analysis of these tools and their application.
The memorization of keywords, mechanics, principles and patterns is an optional skill. To think and to foresee is a good skill.
But instead of learning things that seem important to us, we are gaining skills that are important to the market. We turn into kiddies, imprisoned not for work head, but for the decision of the Unified State Exam.
Here is my point:
We not only trade in this market, we still define it. Developers are interviewed by developers, they create lists of requirements and questions for candidates.
Boys, that's enough. Talk to the person. Ask what I did, how and why.
Do you want to understand that this is not an impostor? Give a very small test task. If you do not have a hundred lines of code to understand what kind of developer it is, you may not be good enough for an interview.
And yes - now, until I have my code behind me, I will not go to the office.
It may be interesting
Situs QQ Online
Situs QQ Online