Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
OK
Systemantics: How Systems Work and Especially How They Fail Hardcover – January 1, 1978
- Print length192 pages
- LanguageEnglish
- PublisherWildwood House Ltd
- Publication dateJanuary 1, 1978
- ISBN-10070450331X
- ISBN-13978-0704503311
Similar items that may deliver to you quickly
Product details
- Publisher : Wildwood House Ltd; First Edition (January 1, 1978)
- Language : English
- Hardcover : 192 pages
- ISBN-10 : 070450331X
- ISBN-13 : 978-0704503311
- Item Weight : 8.5 ounces
- Best Sellers Rank: #8,560,140 in Books (See Top 100 in Books)
- #2,643 in System Theory
- Customer Reviews:
About the author
Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The author refers back and forth to these common systems as it explains over 20 truisms of systems, especially large ones. Some of my favorites include:
- First rule of systems design: do without out one if possible
- New systems mean new problems
- A large system produced by expanding a smaller system will not behave like the smaller system
- Things are as they appear to be, not what they are
The book is written in a very lighthearted yet serious way which makes it easy to read, even funny. Everywhere, things are not working well and those outside of the systems that are failing are sure they could fix them if only their ideas were universally adopted. However, this book admittedly offers no solution. There is no single method to follow and all axioms are too fundamental for direct application. Rather the axioms provide clues and guidance to awareness of what makes a particular system faulty. The Systematics student, understanding the risk of failure, even catastrophic failure, knows that the undertaking should only be begun where the present evil is very clear and the consequences of utter failure are no more unbearable than the original unsatisfactory situation.
Don't take it all in one dose...
The "laws" offered have the level of county lores and layman psychology. If you have drunken two beers you might enjoy it. If you are really interested in how systems work and fail, you only can look away disgustedly. The proposal basically is to avoid systems at all.
The pretentious style of the book was clear for the reader, when after the preface, the introduction and even the second chapter only claims are offered what this book will bring about a great achievement. It never does.
In other words, he gives a lot examples of projects that didn't turn out "as advertised." However, there are a lot of reasons for that. Sometimes people are just outright lying about what a system is for, and it did exactly what the creators wanted, but was sold to the community under false pretenses. That doesn't mean systems don't work, it means we have to be more savvy about what their actual effects will be and not believe the sales pitch about them.
He just fundamentally misses the way systems actually work, because systems only work how they actually work, not how you WANTED them to, or how people HOPED they would, or CONVINCED people they would. They're a lot like programming a computer. A program only does EXACTLY what it does. Exactly what was encoded into its operation. Not your hopes or dreams for the program, just the code written. If the system isn't doing what you want, then you have to change it. That's why you need to plan for iterative evolutions in the system design from the outset and not promise miracles on your first try.
His assertions that systems don't work seem like claiming software doesn't work. It often doesn't work as hoped or intended at first, and yet we all use software exactly because it mostly works for most things most of the time. Given the subtitle claims to be about how systems work, not only how they fail, I think he misses that boat completely. Do not expect this book to improve your systems designs, whether that it what the other intended or not, it doesn't yield that result. Maybe he's just trying to prove his own point in that way too. :)