It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. Today, I picked An Introduction to General Systems Thinking in its 25th-anniversary edition published by Dorset House Publishing in 2001, the original being published in 1975.
Re-visiting so many of Jerry Weinberg’s books in the past couple of weeks has made me realize some lessons I merely had on the back burner in my mind, waiting to be activated. One of these learnings is the Causation Fallacy, best illustrated by this funny video:
It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. Today, we are going to take a look at what I consider the first book in Jerry’s seminal series on managing quality software: Quality Software Management Volume 4 – Anticipating Change published by Dorset House Publishing in 1997.
It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. Today, we are going to take a look at what I consider the first book in Jerry’s seminal series on managing quality software: Quality Software Management Volume 3 – Congruent Action published by Dorset House Publishing in 1994.
It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. Today, we are going to take a look at what I consider the first book in Jerry’s seminal series on managing quality software: Quality Software Management Volume 2 – First-order Measurement published by Dorset House Publishing in 1993.
Quiet quitting is a term that’s been floating around for a couple of months now. Yet, it stands for a concept that’s been around for centuries. Someone goes to work, and is less engaged than she used to be for some reason, eventually starting to look for a new job, and some months down the road you find that person leaving the company for greener pastures – maybe to be the worst on a team again and learn something new, maybe because life circumstances changed, maybe for another reason. Let’s explore my thoughts on this.
It’s been four years since – sadly – Gerald M. “Jerry” Weinberg passed away. Ever since then, I struggled with some public mourning about him, until recently I had just the right idea. On a weekly basis, I will publish a review of a book I read that Jerry either wrote himself or is about some of his work. Today, we are going to take a look at what I consider the first book in Jerry’s seminal series on managing quality software: Quality Software Management Volume 1 – Systems Thinking published by Dorset House Publishing in 1992.
Stick around long enough in the consulting business, and you might notice something I will coin the Arxta-Moment in this blog entry. I’m pretty sure, I’m not the first one to notice this, yet, I’m unaware of someone giving it a name. Let’s explore some history, and look for some advice from Jerry.
It’s been a while since I read from Taiichi Ohno about the Toyota Production System and from Goldratt about the Theory of Constraints. Thus far I thought, both have close to nothing to do with each other. Today, however, I got an insight that brought the two closer together for me. Let me explain.
Just to set the tone straight: I hate traveling for work just like the next person. But today, I’m covering why I hate working remotely even more than that.