Reviews of technical or otherwise work related books I’ve read
★★★★★
Why I read this book: It seems to be popular among the managers in my current workplace. I was always curious what the people that organize the ways we work are inspired by. Plus a colleague read it recently and seemed quite hyped about it.
★★★★★
Why I read this book: I bought this book a while ago, because I felt that my command line skills and understanding of Unix systems is weaker than most of the other senior backenders I’ve worked with. The final push to reading it was moving to the platform backend team. There I encountered more tasks related to writing bash scripts and colleagues sighing deeply at me moving to the beginning of a terminal line by tapping arrow keys multiple times.
★★★★★
Why I read it: One of the few areas where I still feel rather insecure professionally is databases. So I’m always looking for ways to improve myself. Although I have to admit I bought this particular book because it is published by O’reilly and has the word ‘database’ in the title.
★★★★★
Why I read it: I overhear something about different architecture styles here and there, but never had a coherent picture. For example how the typical layered architecture contrast against the onion one? Does Domain Driven Design relate to any of those things in any way? I hoped this book could help me finally build that picture.
★★★★★
Why I read it: I participate in system design interviews as an interviewer from time to time. And unfortunately this is one of my weaker skills. I thought maybe reading a book about system design interviews would help me to understand the nuances of the exercise better and become a better interviewer.
★★★★★
Why I read it: The book is presented as ‘a fun read for those interested in distributed systems’. And I am one of those people. + Kafka is one of the tools used in my workplace, so thought it would be nice to know more about it.
© 2024. All rights reserved.