Twitter | Pretraživanje | |
Joseph Kaptur 5. sij
Odgovor korisniku/ci @danluu
Thoughtful post as always, but I don’t agree with the premise that “algorithms questions are important to big companies because *fancy algorithms* are important there”.
Reply Retweet Označi sa "sviđa mi se"
Joseph Kaptur 5. sij
Odgovor korisniku/ci @danluu
It’s pretty easy to come up with “not bad” algorithms questions, which lets question banks be large, which means memorization matters less.
Reply Retweet Označi sa "sviđa mi se"
Mark Callaghan 5. sij
Odgovor korisniku/ci @danluu
Pagination queries are a common source of O(n^2) in production - Was there new GC pressure from your array resize fix? Growing the allocation by 1.5X or 2X means more allocated but unused memory.
Reply Retweet Označi sa "sviđa mi se"
Dan Luu 7. sij
Odgovor korisniku/ci @MarkCallaghanDB
Definitely could be a problem in some cases, but not in this case. Technically, there was probably an increase in old gen usage (this was on the JVM, using a generational collector), but it must've been trivial, small enough that it was unobservable in aggregate metrics.
Reply Retweet Označi sa "sviđa mi se"
Heath Borders 5. sij
Odgovor korisniku/ci @danluu
Thanks for this post! I've seen a lot of good engineers I've referred (because I previously worked with them for years) get rejected from positions at places I've worked because they couldn't pass a needlessly-hard interview.
Reply Retweet Označi sa "sviđa mi se"
Heath Borders 5. sij
Odgovor korisniku/ci @danluu
The problem with hiring is more general than tech, and is tied to the social stigma with firings and having a proper job history. Over a 6-month stretch, most non-prestigious tech companies could hire better by randomly choosing applicants, and firing bad ones after 6 months.
Reply Retweet Označi sa "sviđa mi se"
Jon Atack 5. sij
Odgovor korisniku/ci @danluu @marionzualo
Often true in engineering tech interviews: the preparation and ability to interview well are frequently uncorrelated with the ability to deliver good work. One workaround is to become a capable freelancer with referrals, social status/network and a good GitHub/GitLab profile.
Reply Retweet Označi sa "sviđa mi se"
Daniel Bilar 5. sij
Odgovor korisniku/ci @jonatack @danluu @marionzualo
This is such a blindingly true statement, it boggles the mind that a typical gotcha tech interview is so decisive
Reply Retweet Označi sa "sviđa mi se"
Chris Granger 5. sij
Odgovor korisniku/ci @danluu
Thanks for the post dan! I’m curious is there a kind of interview that would resonate with you personally? What would the perfect interview look like? One where you felt you could demonstrate your skills and also get a sense for what the company has to offer.
Reply Retweet Označi sa "sviđa mi se"
Chris Granger 5. sij
Odgovor korisniku/ci @danluu
I’d also be really curious to learn more about what made that team you worked on the most productive - I hope you write more about that someday 🙂
Reply Retweet Označi sa "sviđa mi se"