I am a quite good bad programmer
11–20 of 160 posts
Re: I am a quite good bad programmer
#12You'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.
This is so weird. Aren’t you just selecting for obedience and unnecessary hoop jumping? It seems like this would also select the kind of engineers who aren’t willing to say “no, that’s a dumb approach, we shouldn’t do that, here’s an alternative”? When I was a Junior dev one of the first lessons my boss taught me was to always always speak up if something looked off to me. Maybe I’d get an explanation and be enlighte…
This is exactly the reason why any big enough company is eventually going to s*hit
And why founding team doesn’t stay long in a successful startup.
Re: I am a quite good bad programmer
#13You'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.
This is so weird. Aren’t you just selecting for obedience and unnecessary hoop jumping? It seems like this would also select the kind of engineers who aren’t willing to say “no, that’s a dumb approach, we shouldn’t do that, here’s an alternative”? When I was a Junior dev one of the first lessons my boss taught me was to always always speak up if something looked off to me. Maybe I’d get an explanation and be enlighte…
Maybe that’s what they want, namely a self selection of devs who will be happy and okay inside an org that is filled with bullshit.
Re: I am a quite good bad programmer
#14Say no more, you're hired.
Re: I am a quite good bad programmer
#15Re: I am a quite good bad programmer
#16Job interviews have a very questionable form of gatekeeping. But it is a very well documented form of gatekeeping. If you want to get good grades at job inteviews, you can practice how to pass that test... I do agree it doesn't reflect the quality of developer you are, but it is what it is...
"Tell me your opinion of the emperor's apparel."
Re: I am a quite good bad programmer
#17You'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.
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 skills to do the job. So they're always going to miss out on people who aren't good at learning arbitrary skills but already have solid development skills. But many big companies seem alright with that tradeoff.
Re: I am a quite good bad programmer
#18Doing well at interviews has low correlation with being good at the job, simple as that.
A given programmer might blaze through an interview task like a superstar, yet take two days to get started on it if it's an actual job assignment.
Everyone can put on their Gets Shit Done hat in an interview, in other words
That is why interviewers ask questions about previous job experiences and contact references.
Re: I am a quite good bad programmer
#19World needs more 1x programmers.
Re: I am a quite good bad programmer
#20I 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.