Find here an overview of feedback:
A Software Competence Lead expressed his appreciation for the book.
“I like that this book explains the concepts, and depicts the rationale of each aspect by examples and clear figures.”
And that is one of things I think is very important, understanding the purpose of all these different aspects of Software Quality.
In April 2024 I received an e-mail from Vietnam, the writer expressed being a fan of my book.
A comment on LinkedIn by a reader of my book.
For non-Dutch speaking persons, it says:
“Ger Cloudt, I’ve read your book. Highly recommended for insiders in software development, but certainly also for those who are responsible for it, but hardly know what it entails. Great book!”
My book serving as inspiration.
An software engineer wrote a blog in which he quoted my book.
A software engineer wrote a blog with the title “Quality vs Time Pressures in Software Development”. It is really nice to see that my book is quoted and referenced in his blog.
A nice post of a reader of the Dutch edition of the book
She summarized the essence of the book and recommended it to be read by every professional in the software industry.
In March 2022 I was invited to provide a guest lecture about Software Quality @ the Eindhoven University of Technology post-MSc program of Software Technology. Despite the lecture was considered too short, I scored an average 4,6 out of 5 for all other aspects evaluated.
A nice post about my guest lecture @ University of Applied Sciences at Salzburg (AUT)
Christian Neureiter, a professor of the University of Applied Sciences at Salzburg (AUT), wrote a nice post about my guest lecture I performed.
Again a positive mentioning of my book on LinkedIn.
During my career I got many questions e.g. from purchasers in the software industry, asking how the maturity of software suppliers can be ‘checked’. To be able to answer that question you need to understand what software quality is. The person mentioning my book is working as a “Supplier Quality Engineer” at a multinational and apparently reading my book helped him in understanding software quality better.
A software engineer who did receive my book as a present wrote a post on LinkedIn.
He wrote that the book was an “amazing read” and pointed out that this is the case not only for software developers, but as well as others in the software industry. I couldn’t agree more.
TIOBE Software posted a reference to my book on LinkedIn.
As TIOBE Software is honored to be mentioned in my book, I am honored to be mentioned by TIOBE Software in their post.
An engineer who read my book, wrote a post on LinkedIn.
This is what I liked about his post: “Because it’s a neat work that completely changes my understanding of quality in software.”
Apparently my book did contribute to the understanding of software quality by this reader.
About the (virtual) book presentation I gave to Bosch Thermotechnology.
31st of May I gave a virtual presentation of my book, addressing the 1+3 Software Quality Model.
The organizer of the presentation posted this nice post on LinkedIn just after the event.
An e-mail received from an reader of my book.
The reader wrote in his e-mail: “Excellent book, well and clearly written, very practical and applicable almost immediately.”.
How nice to receive such e-mails.
About the (virtual) book presentation I gave to Altran.
March-8 I gave a virtual presentation of my book to Altran. Like the Altran-team-manager wrote in his post: “Ger gave an excellent overview of the book and his ideas about Software Quality: it is more than just testing!”. Indeed, that is exactly what the book is addressing, software quality is more than mere testing.
An e-mail received from a software engineer who read my book.
My book was read by this Dutch software engineer who send me an e-mail in which he wrote: “I am pleasantly surprised. Interesting content with a wide area of knowledge that is nice to read.”. Such feedback is, of course, very much appreciated.
A Director of Bosch.io shared a post after the book was published.
Pavlin is a Software Quality Director at Bosch.io and he was one of the reviewers of the book. In his post he wrote “If you manage software teams, especially if you are quality manager this book is for you!”. Addressing that you don’t need to be a software engineer to read and understand the book.
An Agile Master shared a post after the book was published.
Yogesh was one of the reviewers of the book. It is nice to read the following in his post: “I must say that this is an exceptionally useful and pragmatic book, written by someone, who truly cares and takes responsibility to improve the profession.”.