mikymoothrowa

10 ms·

91.
by mikymoothrowa 4y ago
> However, learning leet code, then applying it in an interview shows you have the aptitude to learn quickly. That’s not why they were introduced. Leetcode using tools like hackerrank were introduced because college GPAs were very bad in
92.
by mikymoothrowa 4y ago
Exactly! 10 years ago, I was a strong proponent of leetcode style questions instead of using college GPAs to hire engineers. It’s the ‘Cracking’ idea that has thrown this whole process off. People have started over optimising for the metric
93.
by mikymoothrowa 4y ago
I’ve seen the no-whiteboard list. Almost none of them hire “outside their time zone”
94.
by mikymoothrowa 4y ago
All these people I have in mind are fresh out of college, self taught probably and aren’t old enough to be EM
95.
by mikymoothrowa 4y ago
I am talking about the kind of questions you would get if you went to hackerrank right now and took an SDE interview with any random company. > homebrew sucks and many googlers try to avoid it if possible Huh? What do they use then? I w
96.
by mikymoothrowa 4y ago
> algorithms are useful and learnable, but some companies take it too far. This is my take too. So I don’t see where the disagreement lies. Except it’s not just some companies doing it. All companies paying over a certain threshold seem
97.
by mikymoothrowa 4y ago
> It’s a common thought among my circles that interviewing is the hardest part of being a software engineer - once you’re in somewhere it’s a lot easier I’ve heard a similar sentiment from my circles too. But lately I’ve also met people
98.
Ask HN: What to do about ‘Good at programming Bad at Leetcode’
291 points by mikymoothrowa 4y ago|478 comments