254
The only thing doing tech tests has taught me is that I'm too stupid to do the job I've been doing professionally for the better part of 2 decades. (lemmy.world)
submitted 3 years ago by to c/programming@programming.dev
71 comments fedilink hide all child comments
 

Can't just be me, can it? Currently 0 for 3 on interviews because I can't seem to get past the technical interview/test. Usually because of some crazy complicated algorithm question that's never been relevant to anything I've ever had to do on the job in all my years coding.

Also, while I'm ranting: screw the usual non-answer when given feedback.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 years ago (3 children)

"Here's an icky piece of code, tell me what it does and what you would do to improve it" seems to have fallen out of style, though it's not clear to me why.

Because reviewing code is easier than writing it, unfortunately.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 15 points 3 years ago (1 child)

    I disagree with that as a rule of thumb. I'll take writing 1000 lines of code from scratch every time over deciphering 1000 lines of bad code.

    However, I do you think are right if limited to the ~100ish lines that fit into an hour sized block of interview time. I suspect the other half of the answer is (good) job postings have largely gotten away from hard language requirements. It's perfectly reasonable to hire someone that will need to familiarize themselves with Go or Python or Typescript or whatever. It's not fair to expect someone to analyze code in a language they haven't used on the spot.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •