,
8 tweets,
2 min read
Read on Twitter
Not only is this a good breakdown of how to pass coding interviews, it's also good advice for, you know, writing better code.
I keep telling people that writing the code is literally the least important part of getting a job. But a lot of y'all don't wanna believe it.
I was talking to a friend recently about this. I feel like it's a sign that I'm becoming one of those grouchy old programmers that nobody listens to. Learning to code is hard. But it's also not the only skill you need.
This job requires critical thinking, strong communication, writing skills, creativity, good judgment, time management skills, attention to detail, adaptability, and a very high capacity for learning new things. That's not even a complete list.
You might recognize a lot of these skills as things you already have. They're also important in many other types of jobs that don't involve coding. So the question is why do you think coding interviews wouldn't be trying to assess those things as well as your coding ability?
There's a lot to be mad at about coding interviews. I'm the first person to say they are bad at assessing strong talent and potential. But that's not the same thing as saying "why can't they just look at some code samples and know I'm good enough"?
That second thing actually does happen all the time. And that's how you end up with coworkers who are unreliable. Because they only got evaluated for a small part of what makes a good engineer.
My point is that you should get comfortable with these skills because they are useful. Not only to pass interviews.
