Why I Read this book
I have to be honest, in all my time as a software developer, there are very few development tutorial textbooks which I would recommend. I have purchased many over the years and so many of them have failed to deliver. All suffering from the same issues of poor code samples, failing examples and in the majority of cases just a load of geek waffle.
Many of these books are always in the arena of 800 – 1000 pages of which at most you’d read 50-70 of the pages in total. If you’re lucky there will be 1 or 2 chapters which will really provide you real value. For the most part, these books end up gathering dust on your bookshelf and help to convince friends and family that what you do for a living truly is rocket science and that you must be really clever to have read all those thick books!
What I like about this book
I remember opening up the project and initially reading the code I had this sense I had no real idea what was going on! The code layout and approach were things I had never come across previously! I had this sense of panic and imposter syndrome most developers experience, and I rushed to the Amazon website and thought I need some books fast!
What I learned from this book
Chapter 4 on functions. May need to be re-read a couple of times – I know I did – but it is also the chapter that bring the most insight when understood.
Who should read this book
Denizon's product line successfully integrate IoT, Artificial Intelligence and Blockchain technology to enable efficient, productive, secure and scalable solutions to help organisations address increasing energy demands, ecological impact and Health & Safety concerns of their staff.
Latest posts by Gary Woodfine (see all)
- Book Review: The Five Dysfunctions of a Team - January 10, 2020
- 5 Years of blogging – What have I learned - January 1, 2020
- Book Review: Best Kept Secrets of Peer Code Review - December 31, 2019