What i am looking for is a discussion of the contents in the book which they have kindly made available for free (the book is expensive).
PS: I am always very appreciative and thankful of people who make their knowledge/books/software available for free and am sure they would like us to focus on the core contents rather than ancillary issues (which they doubtless are aware of and cleared with publishers).
FWIW I’m only familiar with the term “pragmatic programmer” because of the book. I don’t think I’ve ever heard it in any other context.
When I saw the post I thought it was written by the same author.
I am advising you to browse/read the book because we (I and a few others in this thread) have browsed/read the book and found it worthwhile (if you are interested in the domain in the first place, of course).
I have seen some silly arguments in my time but you take the cake on "judging a book by its cover" to a whole new absurd level.
I almost sure that "The Pragmatic Programmer" is a trademark so it comes natural to associate the book with either the same authors or the same publisher as the original book.
What i am looking for in this submission is insights/opinions from people working in this domain on the topics presented in the book. For example, the book talks about "Concept/Data Drift"; so what is it exactly, how does a ML engineer encounter it in his data and how does he deal with it over time?