41–50 of 160 posts
A successful entrepreneur, perhaps, but not necessarily a good programmer.
There's really nothing wrong with being dead average. The interview process is backwards in this industry anyway. No need to worry. It sounds like you're doing fine.
Now to be fair to them, I was asked to do a certain task and I failed to do that task. It's pretty cut and dry.
But I also walked away glad they turned me down, because if they're going to try and force me to do something a specific way when that way is inefficient, or troublesome or just plain not the best answer, then I wouldn't really want to be working there anyway.
It's worth knowing that while you have successfully articulated everything, some people will still see your mistakes as red flags for future communication. Some might even assume that you will be making trivial code mistakes, too; despite there being no evidence of that.
That kind of prejudice is common, and difficult to confront.
There is no real need for you to improve your English skills: your writing isn't ambiguous or missing anything. Even so, it's worth recognizing the social dynamic that is likely to happen, and how that affects you.
KISS is “keep it simple, stupid”: https://en.wikipedia.org/wiki/KISS_principle
> I understands the usage of Hash / Map instead of searching arrays and many other small things that actually enhance the code performance I would consider this an assumed skill for any developer with a college degree. It’s basically the point of the entire Data Structures class, which is a degree requirement.
FWIW, actually, one thing I learned in practice that’s wasn’t highlighted in my Algorithms course: overhead (constant C) matters. You can feel good about yourself for choosing an algorithm that scales in O(lg n) time, but if your you ignore the cost of each operation (C) you might be slow. For example: 1. When n is small, an array is almost always better. Arrays have very little overhead compared to even a hash map.…
I went on an interview some years ago and was asked how I'd architect a certain situation with Models and Controllers. I spent some time discussing why that wasn't the right solution for what they were trying to do, and they said thanks but no thanks. Now to be fair to them, I was asked to do a certain task and I failed to do that task. It's pretty cut and dry. But I also walked away glad they turned me down, because…
Being that cut and dry (read: binary) is a problem of its own; and it's probably the more important one to solve.
You're "expected" to study for job interview questions. It's more a measure of willingness to jump through hoops than your competence. Developer interview questions in general has little to do with what you'll do as a developer, and what you're expected to know as a developer.
> It's more a measure of willingness to jump through hoops than your competence. I'd say it's more a measure of how well you can learn an arbitrary skill. They could change it to solving Sudoku puzzles, grading SAT essays, or wood carving and most of the same people who do well in leetcode interviews would pick up those skills and ace the interviews. But you don't need arbitrary skills, you need solid development ski…
World needs more 1x programmers.
>Copy/pastes code snippets from Stack Overflow, Glitch, Codepen, or wherever they find answers.
>Gives credit where credit is due.
>Spends time on things outside of engineering, like hobbies, friends, and family.
>Doesn't act surprised when someone doesn’t know something.
>Willing to admit when they're wrong, and aren't afraid to say "I don't know."
>Doesn't riddicule entire professions within engineering, especially not when in a position of leadership.
I went on an interview some years ago and was asked how I'd architect a certain situation with Models and Controllers. I spent some time discussing why that wasn't the right solution for what they were trying to do, and they said thanks but no thanks. Now to be fair to them, I was asked to do a certain task and I failed to do that task. It's pretty cut and dry. But I also walked away glad they turned me down, because…
How they react to that is telling. I've had interviews where they say "great point, that's exactly the kind of thinking we need!" and other interviews where they take it as a challenge to their authority. The latter is of course a red flag and you should excuse yourself from any further interviews.
Doing well at interviews has low correlation with being good at the job, simple as that.
> Doing well at interviews has low correlation with being good at the job, simple as that. That's true, but only because companies are bad at interviewing. It is possible to do much better than companies typically do at this. It's just a really hard skill to master, and involves more than just standardised testing.