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

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

Personally, I'm biased against people who use 40 year old editors written for a completely different world, when we have modern and far superior tools.

I mean, if you're too conservative to use modern technology, this doesn't seem like the right field to work in.

That said, the vim guys do seem to get good work done somehow...

[ Parent | on HN ]

Re:How to prepare a technical interview (and why good progra... by rgoulter on Sunday October 20, 2019 @10:07PM (#21308828)

> if you're too conservative to use modern technology, this doesn't seem like the right field to work in.

That's just flamebait.

I like vim and Emacs. There are good reasons to use either of them (or e.g. their bindings in "superior" tools).

Still, the quoted "must use vim/Emacs!" is just stupid. The point is that the work needs to get done.

[ Parent | on HN ]

Re:How to prepare a technical interview (and why good progra... by throwaway87378 on Sunday October 20, 2019 @11:38PM (#21309165)

> I mean, if you're too conservative to use modern technology, this doesn't seem like the right field to work in.

That kind of attitude ("why aren't you using <insert personal preference bloated point-clicky IDE released 6 months ago>?") is just as obnoxious as what is in the article.

[ Parent | on HN ]

Re:How to prepare a technical interview (and why good progra... by BurningFrog on Monday October 21, 2019 @12:36AM (#21309379)

I said nothing of the kind.

I wish people hated me for what I actually say, not what they imagine my attitude is :)

[ Parent | on HN ]