How to prepare a technical interview (and why good programmers also fail)

Re:How to prepare a technical interview (and why good progra... by dplgk on Sunday October 20, 2019 @09:05PM (#21308527)

Hard to take advice from an article with a ton of typos.

The interview process seems to favor CS grads who memorize academic exercises and algorithms. It doesn't seem to take into account if you can actually produce a product and write maintainable code. I don't see the point as you can Google just about any solution during the work day, as needed, and real life work doesn't require you to write galaxy-scale algorithms within a 30 minute deadline.

[ Parent | on HN ]

Re:How to prepare a technical interview (and why good progra... by dan-robertson on Sunday October 20, 2019 @10:25PM (#21308888)

I think the author is just not a native English speaker. The typos seem pretty consistent (eg the author thinks chance is spelled change) and there are some grammar errors and unidiomatic phrases but I don’t think it’s particularly difficult to read or that the errors should imply the article is bad. My guess is that the article is a translation to English of an article in Spanish for Spanish-speakers (eg it talks about “international” startups)

[ Parent | on HN ]

Re:How to prepare a technical interview (and why good progra... by rafapaez on Monday October 21, 2019 @03:13AM (#21309968)

You're right. I'm not a native English speaker. That's why I speak in Spanish in my videos. I wrote the article too quickly (which indeed is a summary of the video) and the grammar corrector wasn't very smart with the "changes" things. Thanks for pointing out the typos.

[ Parent | on HN ]