Donald Ray Pollock shows the worst in the lives of the people from Knockemstiff: their bad decisions, their vices, their worse weaknesses… But, he doesn’t judge them. All characters have human motivations and fears. A lot of fears.
At first, I didn’t like the book. It was extremely dark, and I saw a form of unhealthy voyeurism in the way Pollock dug in the worst aspects of life in middle of nowhere America.
But, after reading all these different stories and seeing how Pollock shows that his characters are stuck in a life that they never chose fighting a terrible destiny that everybody can forecast with no difficulty, I saw the empathy that Pollock has for each of them. It would have been easy to just push the reader to hate the bad guys or feel sorry for the poor victims, but the author rarely choose the easy way and will you make feel empathy for the worst asshole and hope for the most hopeless drunkard.
This book gives a very good introduction to the concepts underlying the RESTful way to design Web Services and explains in details the benefits of a Resource Oriented Architecture. The main issue that I noticed is that the examples are kind of outdated. But, it is actually pretty cool to see how much the web evolved in the past 10 years.
If you come across a cheap copy of this book, I would recommend to read the chapters that are about the general principles of the resource oriented architecture and the examples of how to design a well thought web service. The authors are going in great details about why the type of architecture they are advising for makes sense and compare it with other possible designs. It is extremely useful to understand the value of these principles.
The Minimalists do not provide a lot of answers in this book but do two thing that I found really beneficial to me: They ask some good questions and they tell you to trust yourself.
The tone of the book is optimistic and is in favor of experimentation and customization of the experience. It is overall empowering. Maybe, the template that has been defined as the American Dream and forced on us as the perfect way to happiness is not fitting you. And, it’s OK. Try and experiment with other templates and find the one that make you happy. Do not settle for the one that gives you the best chance to achieve happiness. Give yourself the right to be happy now.
A lot of it is kind of vague and kind of generic, but I think that it’s worth the read. It’s a very short volume.
In this article, Dan Schulman speaks to McKinsey about the social benefits of fintech and of the importance of providing access to banking services to everyone.
There are two billion people in the world that live outside of our financial system. In the United States, there are over 70 million people who live outside the financial system. This is a global issue of immense proportions.
Even if the talk contains its fair share of corporate talk, it also gives some interesting stats about the cost of banking for the less fortunates. People “spend as much as 10% of their incomes on unnecessary fees and interest rates.” Or as much as they spend on food.
Colson Whitehead wrote a real page turner. This book is excellent. It is captivating and at the same time gives you a better understanding of the origins of race issues in the United States. It presents a story of a New World built on plundering and violence. It is not a beautiful story and it does not bring a beautiful morale at the end. But, it is a story worth being told.
In this note, Dan Dixon speaks against the impulse to define the benefits of reading and the fear of picking the wrong books. In this article, the author shows his love for books and the act of reading and promotes random book picking and crazy reading challenges. Give a chance to serendipity and pick a […]
A few weeks ago, I posted a note about a tinkering project with the purpose of building a small web API with Flask to get notifications on Slack from my WordPress blog.
At the time, the application was deployed on a Raspberry Pi and I wanted to try and get the application to run on Heroku.
In the process, I adopted some of Heroku best practices on the management of the environment setup. I cleaned the code so that it can be shared on GitHub and I played around with Slack message formatting capabilities.
What did I learn?
At some point during the migration of the application from the Raspberry Pi, I spent a lot of time being stuck with an “unauthorized access” error. I assumed that the issue was coming from my poor understanding of the port routing logic of Heroku. I was wrong, as the issue was linked to the definition of the Slack API Key.
In the process, I learned that the official documentation is often the best place to find reliable information on a service, as the Heroku documentation show me the correct path to the solution.
I also learned that you need to get as much insights as possible from logs and error messages before starting to mess with your code.