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.
On my quest for a good Flask book, I saw this book from Tarek Ziade. We are more or less of the same generation, both from France and he wrote a far better introductory book to Python in French than mine. He also founded the French Python community (AFPY), so I always had a huge respect for the guy. And the book was appetizing.
I’m thinking of writing a Web service for a project of mine. For this purpose, I wanted to learn Flask (and a bunch of other technologies), as Flask seems well established and well documented. This is a book from Packt that agglomerates 3 previously released books. One of the main questions is the relevance of them as the Flask API evolves.
All major cloud providers provide some support for Machine Learning algorithms. They also evolve all the time. There are not many books ont he subject, due to the evolution of these services, so let’s have a look at this one.
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.
A decade ago, the objective was to have a build farm and do continuous integration (on each commit, build the application and run unit tests). Now, the objective is continuous delivery. This means that the new build is directly put into production. All the major applications are doing this, from Chrome to Spotify. You may not get every version on your machine, but you should consider a build as something you could deploy.
The nice thing is that there are tools to ease this workflow.