I watched a YouTube video recently on writing a (nonfiction) book, and the vlogger was talking about this book. As an avide reader, I have been sometimes frustrated by some of the my reads’ storyline. Could this book help me?
I had to wonder. In my previous computer science positions, my coworkers were rarely computer scientist majors. They had a varied background, like chemistry, and I have myself an odd background (majored in signal processing, digital electronics and automation, then music and also a PhD in machine learning in partnership with a neuroscience lab).
In finance, lots of people are finance first and only, and they take everything at face value. Then came Epstein’s book. Could it explain what I was seeing?
I’m fascinated by startup founders. These guys decided to jump in the unknown, with an idea, and they battled through adversity. They don’t always succeed, but enough do so that we think “what if I had an idea?”.
I always wondered what was wrong with me, why I needed to sleep 8 hours a day, why less than that would make me insufferable, on edge and less productive that I’d like. And then I found this book.
And it seems I’m normal.
Have you even wondered what happen in 2008 on the markets? Why did so many people lose so much money? Why did the banks need saving? Behind all crisis, there is a story, this is what this book tells.
What’s the common point between the questions of cryptography (US and Australia), vaccines (and link to disease), vitamin C (to cure cancer), spending thousands on power cables for your sound system? Some people use their non-knowledge to bully experts. And I think this book answers the question of why this happens.
A few weeks ago, I presented my work on automatic code generation from an electronic schema. I have many things to talk about this subject, one of them is this book.
When you start analyzing a circuit, it is important to learn how to analyze a circuit. There are lots of books on electronics, but this one targets beginners in circuit analysis.
I work on a day-to-day basis on a big project that has many developers with different C++ level. Scott Meyers wrote a wonderful book on modern C++ (that I still need to review one day, especially since there is a new Effective Modern C++), but it is not for beginners. So I’m looking for that rare book with modern C++ and an explanation of good practices.