Leetcode isn't programming. Leetcode is pattern-matching which rote-memorized algorithm will solve a problem in the expected time/space. If you want to get better at programming, find some side projects you're passionate about and make time to work on them (if you can). If you want to get better at leetcode, force yourself to do them N hours per day. If you find both of these distasteful, you'll have trouble in your dev career, and might find management more enjoyable.
It's not sprint planning, 1 on 1s, backlog grooming, jira tickets, slack support, gathering requirements, making estimates, negotiating features with management, responding to alerts, or the million other things you get sucked into as a nominal "software engineer".
But it's definitely programming.
It's a specific style of working, not entirely unlike TDD, with a specific theme of problems which aligns well with the content of undergraduate algorithms and data structures courses.
Is there a degree of pattern matching and rote memorization? Most certainly!
And does pattern matching and rote memorization play a significant part in real world programming? Definitely! If there's not as much memorization happening it's because the art of copy and pasting from stackoverflow supplants the need.
And presented with wishing to learn the content of a university course, what's one rather effective technique to achieve it? To do exercises, a lot of them, and when you're stuck look at how other people solved them.
That's all leetcode is.
Perhaps others think that undergrad course in algorithms and data structures is useless material but I do not. I think it makes you a better programmer.
I think a better way to phrase what the parent is saying is that Leetcode is not software engineering. You can be awful at solving leetcodes and still be a great software engineer.
Now, do I think algorithms and data structures make people better programmers? Absolutely. But I feel like most people work on in an area like web development where the usefulness of it is severely reduced when you are working at such a high level of abstraction.
I agree. Memorizing algorithms to answer leetcode questions have their benefits but it’s extremely rare that a front end web developer would need those skills. If they did, that would mean the backend engineers aren’t using the right approach to organize and serve data to the client.
Perhaps "leetcode isn't programming" is hyperbolic, and philosophically arguable, but what's 100% clear is leetcode uses a different skillset from real-world programming, and if you want to get better at one, doing the other won't help.
Spring planning, backlog grooming, etc. are not the examples I would use if I wanted to support the opinion that leetcode is not a real programming. (I definitely agree that some knowledge of algorithms and data structures can be very beneficial.)
My examples would be activities like building complex systems, maintaining and extending them, making them modular and flexible enough, doing performance analysis, identifying risks, and addressing technical depts, considering and implementing different architecture patterns, creating efficient CI/CD pipelines, automating routine.
you are wrong. it's not. it's simply memorizing optimal solutions to obscure programming challenges. the goal is to reproduce the optimal solution within a few minutes. nobody can do that, unless you memorize what the optimal solution is. the reason leetcode has become popular is because that gayle woman lobbied herself into a position of power at google and then wrote a book so she could profit from a "problem" tech companies think they have.
Thank you, I'm definitely not giving up on the LC I just need to figure out how to build a solid foundation for it.
As for career, I really enjoy building products. At work I've been the lead on a few end to end full stack projects that I'm very proud of. I like to set up projects and then get a lot of pride feeling knowing that in the future other developers will be extending this base project as it grows.
I am trying really hard to find a job where it involves understanding the customer and business needs (I really like to get on calls with our product manager/designer, and then work together to develop and test the solution), and building the best product. My favorite feeling is shipping something that people find useful, so idk which companies or what roles would really let me shine best there. One of my goals is to get better at networking, to see if I can get some job like a technical co-founder of a startup I think that would be a dream for me.
If you know anything let me know, I'll check it out. Sorry for blurting out a lot of details I guess I'm just feeling defensive still after that mock interview lol. I feel like how can I be a co founder when I cannot even pass a Leetcode?
Working through Skiena's Algorithm Design Manual [0] would be a good start and/or watching his lecture series on Youtube [1].
Other great books include Elements of Programming Interviews [2] which comes in Java, C++, and Python flavors.
It can help to focus on a smaller subset of Leetcode problems to learn the tricks that underlie most of them. Neetcode [3] is a good collection of those problems on which you could focus your time and efforts.
I don't think it's realistic to expect to do well on Leetcode without practicing the above skills to some degree, so I wouldn't be hard on yourself if it's been years since you even looked at the material.
Don’t give up. The parent comment is very much inline with how I feel. I was in your shoes a couple months ago and passed interviews at 3 faangs. Just grind the leetcodes. Course are not the right way imo. Repetition and pattern matching will take you there.
