Hey everyone! I'm feeling a bit overwhelmed with all the programming resources out there, and I'm on a tight timeline. I'd really appreciate some guidance from those in the industry. I'm a non-CS graduate with a law degree, not from the U.S., and I've just received an offer from FDM to join their software engineering program, which starts on January 19, 2026.
FDM offers a 3-month full-stack training program before helping you find client placements, mainly in banks, using a tech stack of Java, Spring, and React. I've completed CS50's Python course and can code in C, Python, and JavaScript (though my front-end skills need work). I'm passionate about software engineering and have projects in my portfolio.
I've collected a bunch of books to read, such as:
- SICP (JS Ed.) by Abelson and Sussman
- The Pragmatic Programmer (20th Ann. Ed.) by Thomas and Hunt
- Clean Code (4th Ed.)
- Operating Systems Concepts (the Dinosaur book)
- The Dragon Book on Compilers
- And more on Java and OOP.
But now I'm confused about the order I should tackle these in. I know data structures and algorithms (DSA) are crucial for interviews, but I've also heard they don't help much on the job. I enjoyed reading *Grokking Algorithms* and *Grokking Data Structures*, but they're just general overviews. I tried using Leetcode and Neetcode for practice, but I find the explanations lacking.
So my questions are:
1. What order should I read these books in?
2. Which ones should I focus on to improve my Java skills?
3. Do I need to tackle Algorithms by Sedgewick and Wayne, and how important is it for my job?
4. Any good alternatives to Leetcode and Neetcode, since I'm not grasping their explanations?
3 Answers
Diving into LeetCode without a solid grasp of DSA might feel overwhelming, so I'd suggest checking out *Beyond Cracking The Coding Interview*. It offers a structured approach and could help you pinpoint areas to focus on for your interviews.
I totally get that 'analysis paralysis' feeling! Juggling so many complex topics can leave you overwhelmed. A more sensible approach might be: start with OS fundamentals, then Java basics, followed by code design practices, and finally dive into DSA and interview prep. This way, each concept builds on the previous one.
Thank you! This structure really helps. Quick question: Is *Operating System Concepts (Dinosaur Book)* too challenging as a starting point, or should I consider *Operating Systems: Three Easy Pieces* for an easier introduction? Also, how should I approach learning Java through books like Core Java before jumping to Effective Java?
FDM's training will set you up pretty well for the initial months. Honestly, your preparation seems solid! With your non-CS background, you're in a good spot since you can avoid some bad habits. I’d start with Java and Spring since those are central to FDM, and you can tackle DSA after getting comfortable with the basics. You got this!
I appreciate the encouragement! Were you in the FDM program yourself?
Thanks for the suggestion! I saw mixed reviews about that book online. Do you think it really offers valuable insights despite the criticism?