I just got a nice email saying Beyond Cracking the Coding Interview was really helpful not only in the technical aspects but also in the 'psychological' aspects.

Writing from a place of empathy with the reader is something I learned from Mike Mroczka. I come from an academic background where it's all about information density and, sure, being succinct is important when writing a book, but:

- It is also important to recognize that job search is a frustrating experience, and it is normal to deal with burnout. That's why we have a section on making your job search more sustainable.

- It is also important to call out explicitly when a problem solution uses a 'trick' that you'd have no chance of coming up with on your own, and that you'd be screwed if you hadn't seen it before.

- It is also important to set realistic expectations and not make it look like there's something 'wrong' with you if you fail an interview. That's why we open the book with a story from each of the authors about how *we* failed a coding interview.