Live data from Hacker News

A guide to learning algorithms through LeetCode

github.com

41–50 of 222 posts

Re: A guide to learning algorithms through LeetCode

#41
post #38

Gosh, I don’t enjoy that there is so much competition in this space. I can’t compete against people who essentially seem to have no life or other interests than getting job at Big N (or enjoy competitive programming). It feels like this culture has ramped up in the last 5-10 years. When I started interviewing, the questions were easier. It feels like they’ve gotten more difficult - or at least the answer the intervie…

[deleted]

Re: A guide to learning algorithms through LeetCode

#42
post #4

Thanks for the write up and git book. Related question: I’m curious if any has game-ified algorithm learning, sort of like those old educational math games targeting certain grade levels. Might be cool to make a point and click adventure centered around dynamic programming or greedy algorithms.

There are plenty of competitive programming sites where you can grind rating just like you would for MMR rating in video games.

For example CodeForces, AtCoder, TopCoder, and even LeetCode have rated contests

Re: A guide to learning algorithms through LeetCode

#43

Can you imagine having to learn all this just to make a connection to a database, process some data, and then persist it somewhere?

But it might come handy when implementing - route optimization problems - Building database query optimization engine You can argue that not everyone is implementing these from scratch every day. But it could be argued that given an opportunity, an engineer should have the skills and ability to build these systems.

Bullshit.

It has been my personal experience, and the experience of many people I’ve spoken with, that this kind of trivia is learned in order to get a job and then forgotten immediately afterwards because it’s useless.

Anecdotal example: a former colleague is an incredibly talented systems programmer and has had to study leetcode garbage for the last few months in order to feel qualified to interview for a position with a team that he had previously been on at an older employer.

As another commenter said elsewhere, these types of questions are used because they’re legal proxies for “IQ tests”, and because they filter for people who are willing to sacrifice much of their personal time for the sake of the company.

Re: A guide to learning algorithms through LeetCode

#44

Can you imagine having to learn all this just to make a connection to a database, process some data, and then persist it somewhere?

But it might come handy when implementing - route optimization problems - Building database query optimization engine You can argue that not everyone is implementing these from scratch every day. But it could be argued that given an opportunity, an engineer should have the skills and ability to build these systems.

[deleted]

Re: A guide to learning algorithms through LeetCode

#45
post #22

Earlier quoted context omitted.

I wonder if that isn’t the point, to increase developer retention and reduce competition for devs.

It would be a "tragedy of the commons"-like effect for companies that don't adhere. I would guess that is just an unintended effect and that there is no master plan behind making recruiting expensive, slow and inaccurate.

Or it's part of an organised cartel between the major SV employers to reduce salary competition and employee turnover.

https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...

Re: A guide to learning algorithms through LeetCode

#46

It's becoming obvious to me that my time is better spent learning to solve these riddles rather than actually becoming a better developer. I have a job search coming up at the end of the year and whilst I've managed to largely avoid companies that ask this type of question, I believe it's seriously constraining my career. I can't speak for everyone but the whiteboard interview has prevented me from leaving jobs earli…

I was working on a “startup”/kinda just unemployed for two years. I studied leetcode hard, and got hired into a 300k a year job at FAANG. I know nothing about testing, git, software process, roll outs, dev ops, etc. I barely know how to do software engineering. What an idiotic hiring process.

How did you get past the resume screening? Or are you from the US, because then it's much easier to get past the screeming, or so it seems.

I have yet to be invited for so much as an HR call when it comes to FAANG (bachelor/master CS from a Dutch university). Maybe I'm not getting past the application tracking system?

Re: A guide to learning algorithms through LeetCode

#47
post #40

Earlier quoted context omitted.

I was working on a “startup”/kinda just unemployed for two years. I studied leetcode hard, and got hired into a 300k a year job at FAANG. I know nothing about testing, git, software process, roll outs, dev ops, etc. I barely know how to do software engineering. What an idiotic hiring process.

Do you think it's unlikely for you to learn those skills quickly? People who have all those skills earn over $300K at those companies.

To be fair, a lot of people who have none of those skills also earn well over $300K at those companies. Just like grinding leetcode can get you in the door, the skills you need for advancement are not necessarily the same ones you need for making good software.

I hope the parent makes the best of it and becomes good at the craft, it will make the job a lot more enjoyable even if it may not be the fastest way up the ladder.

Re: A guide to learning algorithms through LeetCode

#48
post #40

Earlier quoted context omitted.

I was working on a “startup”/kinda just unemployed for two years. I studied leetcode hard, and got hired into a 300k a year job at FAANG. I know nothing about testing, git, software process, roll outs, dev ops, etc. I barely know how to do software engineering. What an idiotic hiring process.

Do you think it's unlikely for you to learn those skills quickly? People who have all those skills earn over $300K at those companies.

It’s been really stressful. I know python, but not really any other languages. I’m able to get work done. But I’m really nearly the same as a fresh grad. But really, I was just bumming around, then studied for four months and destroyed their algorithms questions, so much so that expectations for me are really high. But all I know is leetcode, literally nothing else...

Re: A guide to learning algorithms through LeetCode

#49
post #8

This is really cool. What order are the chapters in? Seems intense to lead with dynamic programming.

I got really good at dynamic programming problems but then none of the companies I interviewed with asked me a dynamic programming problem. These were large tech companies and well funded startups. Perhaps it was just luck.

DP solutions were really in vogue for awhile, and seem to be asked less now. I heard a completely unsubstantiated rumor that FB found them to cause high false negatives because they're such a tricky and specific problem type. Also, once you know the "one trick" to solving them they don't help illuminate candidate thinking.

Re: A guide to learning algorithms through LeetCode

#50

Earlier quoted context omitted.

I was working on a “startup”/kinda just unemployed for two years. I studied leetcode hard, and got hired into a 300k a year job at FAANG. I know nothing about testing, git, software process, roll outs, dev ops, etc. I barely know how to do software engineering. What an idiotic hiring process.

How did you get past the resume screening? Or are you from the US, because then it's much easier to get past the screeming, or so it seems. I have yet to be invited for so much as an HR call when it comes to FAANG (bachelor/master CS from a Dutch university). Maybe I'm not getting past the application tracking system?

The recruiter just reached out to my LinkedIn profile. My understanding is it’s really easy to get the interview
Post reply on HN