Now adays most read work (IT) related books.
Prefer physical books over e-books. Seems I never get around to reading the e-books. Out of sight out of mind?
Also on Mastodon: @HenrikRxn@hachyderm.io
This link opens in a pop-up window
The author writes in an clear and mostly easy to understand way, but on occasion the metaphors get a little out of hand.
But the book is a good introduction to how you need to change your way of thinking when going to the cloud
Found the book to be a bag of mixed nuts in the sense that I have followed the "Observability" area for some time now so a lot of the content is not new to me.
But if you are looking for a good, easy to read introduction to "Observability" then this is a five star book. If you on the other hand are well-versed in the area then I would say it is a three star book, but there are useful chapters even if you have the basics in place.
I read the 1st edition back in 2008 and then it was about the only book about agile covering both the process and the technical side.
The 2nd edition still has both, but also a new concept of "zones" of agile ability that make it clearer what can be done to focus of each ability.
I would recommend this book to anyone who wants a well structured take on what is needed to become agile. I have seen far to many projects that were agile in name only and agree with Shore's approach of "follow my book to the letter, see it work after some time and then adjust"
Found some of the ideas interesting, while disagreeing strongly with others. Basically same feeling as with "Clean Code", but found this book a little less valuable.
Consider some parts (general concepts) valuable, but find some of the views very religious without much foundation besides the authors beliefs / observations from teaching classes. In my experience the code you write while at university is very different because it has a much shorter lifespan (usually a course) and is much simpler + you are not very experienced as a "developer".
If you read this book as the gospel I would say you are only getting half the value and will end up getting, in my opinion, a lot of bad advice.
But if you read it with an open mind and reflect on the concepts and advice given you'll be a better developer.
Introduces a lot of concepts and techniques you can use, but also looks at the broader picture such as communications.
A lot more applicable (and practical) advice compared to e.g. the books by Len Bass.
Even bad code can function. But if code isn’t clean, it can bring a development …
Consider some parts (general concepts) very valuable, while a lot of the advice on how to use the general concepts in practice is opiniated and, IMHO questionable at best.
If you read this book as the gospel I would say you are only getting half the value and will end up getting, in my opinion, a lot of bad advice.
But if you read it with an open mind and reflect on the concepts and advice given you'll be a better developer.
For twenty years, the lessons from The Pragmatic Programmer have helped a generation of programmers …
Read the first edition a couple of years after it was published, I had been working professionally as a software developer for about 4 years, but still and learned a ton from the book.
The 20th anniversary edition has been updated a little, but because the main points are general concepts and techniques not tied to specific technologies they are still as valid today as they were when the first edition was published.
If you prefer technical books that focus on general concepts applicable across technologies rather that detailed information about how to apply a specific technology then this is a book for you
Whether it's in Java, .NET, or Ruby on Rails, getting your application ready to ship …
Was ahead of it's time and introduced many novel concepts and was an eye opener for me when it comes to designing and developing distributed systems.
There is a Second edition from 2018
