There is a book called Grokking Algorithms (forgot the author), it's a more gentle intro to algorithnd, I would strongly advise that book for someone that completed a bootcamp.

For a gentle introduction to algorithms and Big O, "Grokking Algorithms" is easy to read and fun. For more in depth and systematic study, Sedgwick's "Algorithms" is a very clear and beautiful book.

For computer architecture, Petzold's "Code" is wonderful.

Grokking Algorithms by Aditya Y. Bhargava (I believe he's on HN). Highly recommend, easy read and really enjoyable.

I like Grokking Algorithms (pdf only, book done in december).
It's quite easy to understand and start with, compared to other algorithms books I have seen.

Don't Make Me Think (200 pages)

Grokking Algorithms An Illustrated Guide For Programmers and Other Curious People (235 pages)

Disclaimer: Googler here.
There are many ways to land a job at Google:

1 - work somewhere else then after couple of years of xp in a field try to find a job opening that matches your xp (that’s how i got in).

2 - if you are in Uni, apply for internship. We always welcome interns.

3 - apprenticeship: there is a program so that you can start working after college. I know some people went this route and are now full time employees.

4 - other ways like PhD etc...

Bottom line is: you don’t need a fancy uni (I did a state uni in france). What’s important is that you are good at what you do and you do it for yourself, not just to work in a FAANG company.

Tips:
Skills that Google is looking for: critical thinking, collaboration, communication, analysis of trade offs and being a genuinely nice person.

Books that got me into Google:
The Algorithm Design Manual by Skienna
Grokking Algorithms by Aditya Bhargava

Hey! If anyone's interested in an intro to algorithms, I'd like to pitch my book Grokking Algorithms[1]. It is an illustrated guide with a focus on being easy to read. I've gotten a lot of comments about how easy it is [2] [3] [4].

Sample chapter here [5].

[1] https://amzn.com/1617292230

[2] https://twitter.com/cachilders/status/746522721794691073

[3] https://twitter.com/ashkrit/status/745636106163478529

[4] https://twitter.com/bertrand_cachet/status/74369502984414003...

[5] manning.com/bhargava

I enjoyed the audiobook versions (while following along with or having already read the written version) of Grokking Algorithms and Classic Computer Science Problems with Python

Constantly.

I don't mind high level videos to give a 10,000ft view but for everything else the written word wins every time.

Currently re-reading A Philosophy of Software Design and just started "Grokking Algorithms" alongside the 2-3 fictional books I have on the go at any given time.

Glad to see I'm not the only one who thinks this - it's one of the many areas I need to look at, and saw that recommended elsewhere... took a look on Amazon and got completely intimidated! If 1000+ pages is an introduction, what does the chapter and verse look like?

(I've started reading Grokking Algorithms this week, and it's been a much better introduction - I know it's not as in depth as some other books, but I'm making good progress with it and not drowning in complexity from the get go)

Is there any chance you (William) could add hand-drawn illustrations and flow-charts? :) This makes a book outright welcoming IMHO. I loved that style in Grokking Algorithms (or even in Getting Started in Electronics by Forrest M. Mims III, if you want a distant example).

Thanks for your initiative, will buy the book soon as it is available.

I've written a book with Manning (Grokking Algorithms) and had a good editor experience: I had 2 editors that stayed with me through the whole book. They gave me a ton of great advice -- I even asked one of them if they would like co-author credit, it was that good. Manning regularly scheduled technical reviews and readability reviews, and I got a lot of comments from those as well.

I have also only written one book so I wasn't sure how "typical" my experience was, but I'm really surprised to hear that your book didn't receive the same level of support!

There's another book from this publisher called Grokking Algorithms. That one left me very impressed. Usually, I don't care for any "simplified/easified/dumbed-down" books because they often feel like a compilation of buzzwords with all the important bits removed. I thought Grokking Algorithms was simple, yet very meaty/substantial if that makes sense.

I've read a few of these and agree. Zero to One, I really enjoyed this when I read it. Sapiens was also fantastic, I want to re-read it.

I also got Grokking Algorithms this year. I already have a few denser algorithm books, but I really liked this one for the basics. I bought it as a refresher that wouldn't be as dry as reading CLRS, and because I've been recently helping a friend who is beginning a CS degree.

> Mastering Selenium WebDriver. This is probably the only good book on Selenium among so many bad books on this topic.

I have to work with Selenium a lot, and you're right, there are so many terrible books and articles about Selenium. I'm going to look into this one, thanks.

Bought it. Pretty basic stuffs:

- Didn't learn anything new from Linux chapter.

- Data Structures and Algorithms chapter is too basic. There is not even any implementation provided. I thought it didn't offer anything more than you could find on Wikipedia if you add some illustration done with Paper by 53 app. I'd recommend "Grokking Algorithms" by Aditya Bhargava for this topic if you want illustrated explanations with brilliant examples.

- Didn't learn anything new from Databases chapter.

- Didn't learn anything new from Programming Languages chapter. Inclusion of useless things like TIOBE Index made me furious, honestly.

- Didn't learn anything new from Software Design chapter.

I won't recommend this book to anyone working in software engineering for more or less 5 years with or without CS degree. This book merely serves as an index of what you'll encounter in the field, nothing more than that. Not even any good elaborations on those topics. Pretty meh.

> The Algorithm Design Manual and Algorithms: Fourth Edition are both books I picked up back in the day to refresh some of the my university algorithm class studies. I gave up midway, and found them pretty dry, and not applicable to my day-to-day work.

These are both good books that I actually like! They aren't quite as massive or comprehensive as CLRS but are easier to read as a textbook. I also like Steven Skiena's course videos. But I agree completely that they are unlikely to be something you'll use day-to-day unless you work as an algorithms specialist.

> Grokking Algorithms by Aditya Bhargava... I am convinced that you don't need to know more about algorithms than this book covers.

This is a nice and compact book, and I think he's right for most jobs that involve writing software. Won't be enough to get you past the idiotic algorithm puzzle interviews though. ;-(

Grokking Algorithms (https://www.manning.com/books/grokking-algorithms), preferably on paper.

I think _terrible _ might be a bit harsh on Grokking Algorithms, but most of it’s curriculum is rather basic, and the few last chapters about graphs, which I’d say is a bit less basic, pretty much require that you inspect the accompanying pdf with illustrations… this might not be a problem of you’re listening while sitting in a train, but it will be a problem if you’re listening while walking the dog (like me).

I would just describe Grokking Algorithms as a bad book, and mostly relevant if you have zero prior experience with Algorithms.

Oh, and the narration of the code snippets is also pretty useless IIRC.

Ok, while writing this, I realize that “terrible“ might actually be well deserved.