4 ms·
The issue with this is that you would be surprised at how some people are good at “talking” but when it comes to doing something simple with code aren’t able to
by Google234 6y ago
The issue with this is that you would be surprised at how some people are good at “talking” but when it comes to doing something simple with code aren’t able to backup their supposed skills
- siscia 6y agoAfter working for several years in reputable organisation, how bad can somebody be at coding? Yes there is still a tiny possibly that it is just a talker, but such possibility seems much smaller than the possibility that it pass a coding interview on a whiteboard and then he is not that good.
- Google234 6y agoWell, this interview process seem to select for the best talker which I don’t think is the optimal signal for a dev. I know many super competent engineers that aren’t the best English speakers
- siscia 6y agoI believe you are (intentionally) missreading and misinterpretating what the comment and myself are stating.
- SamReidHughes 6y agoThat depends on what you mean by reputable organization. It also depends on what your bar is. Some companies could use "was a Google employee" as a sufficient qualifier, but for others, that wouldn't be enough.
- Cthulhu_ 6y agoDepends on what you consider "reputable"; I've worked with people at a large bank doing some great apps and the like, but they were incompetent. The college project thing applies to the workspace as well; in a team or a project there's always going to be only a few or one that does the most and best work, and a lot of hangers-on. That is actually a source of impostor syndrome for me, because if I look at my CV there's a lot of really interesting and varied stuff on there, but it was always me as part of a team. How much of what I contributed was original thought vs just copy / pasting someone else's work and changing some values? That's said impostor syndrome speaking of course, I know I'm a competent developer and ATM I'm working solo on a project. Slowly.