Do live coding interviews or else(sheepcode.substack.com)
sheepcode.substack.com
Do live coding interviews or else
https://sheepcode.substack.com/p/do-live-coding-interviews-or-else
4 comments
If I need to do something in Python then I more than likely google for the answer. I can't remember all the foobar syntactic subtleties off the top of my head and neither can most people. So when you give some random quiz to trip the interviewee up to expose them as a fraud that is when I'd get up and leave. I'm not going to be interviewed to prove I can write code because I am probably more experience than you.
That’s not the intent at all whatsoever and is no where indicated in this post.
I am the author. Thanks for sharing this. Please roast me.
I like your honest tone and upfront attitude. As someone who left the industry because of this type of thinking I’d like to say it’s half-correct.
Patterns and anti-patterns are something which help make useful software. Not only architecture patterns like MVP or MVVM, but design patterns like a factory or builder etc.
It’s my belief there are also developer patterns and anti-patterns. The slacker pattern isn’t an anti-pattern, but often can incur the team pattern of daily iteration vs. bursts of work.
Most of what you’re discussing seems slated towards the anti-pattern of “words without code”. Which personally I believe is also an anti-pattern. The code must come, otherwise it’s not work, right?
But when you talk about these people “they hate tests” “doesn’t want to do X and Y perfunctory thing” your team isn’t presenting the value of those things first and foremost. Have you tried putting a “sheep” and a “slacker” together?
Patterns and anti-patterns are something which help make useful software. Not only architecture patterns like MVP or MVVM, but design patterns like a factory or builder etc.
It’s my belief there are also developer patterns and anti-patterns. The slacker pattern isn’t an anti-pattern, but often can incur the team pattern of daily iteration vs. bursts of work.
Most of what you’re discussing seems slated towards the anti-pattern of “words without code”. Which personally I believe is also an anti-pattern. The code must come, otherwise it’s not work, right?
But when you talk about these people “they hate tests” “doesn’t want to do X and Y perfunctory thing” your team isn’t presenting the value of those things first and foremost. Have you tried putting a “sheep” and a “slacker” together?