Please create an account to participate in the Slashdot moderation system


Forgot your password?

The Trousers of Reality 63

gregrolan writes "The Trousers of Reality — Volume 1, Working Life is indeed a book about finding balance and satisfaction in life work and play. The author's thesis can be applied to almost any discipline, but it is from his background as an IT consultant that most of his professional examples are drawn. He considers success in this field pretty broadly and addresses the technical, management, political, personal, and social aspects of the IT profession." Read on for the rest of Greg's review.
The Trousers of Reality - Volume 1: Working Life
author Barry Evans
pages 294
publisher Code Green Publishing
rating 8
reviewer Greg Rolan
ISBN 978-1907215001
summary Find balance and satisfaction in life work and play
Rather than expound upon the virtues of Yet Another Methodology or a Prescribed Practice, the author sets out to show that the wisdom and experiences of the last few millennia have lead to principles and practices that transcend particular methodologies or approaches and form the basis of success; that introspection and empathy will serve better than adherence to position and retreat behind logical argument; and that, ultimately, we all want similar outcomes — even if it's not obvious on the face of it.

If you have ever been torn between deadlines and burnout, stretched between politics and technology, or simply wondered "How am I going to get through this?" I think that this book definitely has something to offer you.

Firstly: a disclaimer. I worked with Barry Evans for approximately nine months about fifteen years ago in London. We kept in touch, sporadically, after I returned to Australia and, over the years, I followed his career from Software Engineer to Team Leader to Organizational Project Mentor to his own Practice Consultancy business throughout Europe and beyond. What struck me in retrospect was that, in the mid-nineties, Evans was doing Agile — not that it had a name back then, or even that we recognized it as such. He talked philosophy, was passionate about practice and meaning and we delivered (on time and in budget) which was surprising given the nature of the project. This was a pattern that he would come to repeat within many projects and organizations.

When he announced that he was taking time out to commit his experiences to paper, I admit I was keen read his book. It turns out that this is the first volume in a series of four and addresses developing a set of principles to guide working life. The other three (yet to be published) cover how to use these principles; specific examples of their use; and the principles in broader contexts — relationships, society and the world.

The first thing the reader notices about this work is the breadth of the material drawn upon in order to build the author's arguments — ranging from historical, contemporary, technical and personal sources. The second is the copious footnoting and rigorous referencing of other works. This in itself is valuable allowing the reader to delve deeper into particular themes if they wish. The book is supported with additional material at the author's web site

The main body of the book opens with the short chapter "Themes, Directions and Koans" which outlines the broad ideas and concepts of the volume. It's a pretty starkly written chapter — the first few pages in particular are daunting — but soon you realize that the book is written somewhat fractally. Concepts are stated, revisited and linked with others into a whole, adding details as the iterations progress. In fact the book itself is a good example of the author's themes: "Evolution and Interconnectedness" and "Universality and Context" — the other ones being "Reciprocity and Balance" and "Longevity and Inspiration". Here, the themes are introduced, connected and linked with the tools one needs to begin to address them.

"The Most Important Chapter In This Book" follows next and introduces the idea of "Deep Structure and Surface Structure". Most of our activities in professional and personal life involve discerning others' expectations and perspectives and working to accommodating them. This chapter accounts for differences in perspective we have in relation to even commonly held ideas. It explores the conflicts that may arise due to this duopoly and shows how the evolution of ideas and practices give rise to the paradox "The more we know, the less we know". It also lays the foundations of understanding prejudices and the mechanisms of socialization of ideas. None of these concepts are new, but are drawn together in forehead slapping clarity. This, I think, is what makes this book accessible, the author's ability to describe an easily digestible deep structure from seemingly disparate surface structure concepts.

The third main chapter "The Map" draws the distinction between process and principle and gives guidelines on how to form one's principles for professional and personal life. As the author explains, this is a process of "differentiate[ing] between opinion and observation", and "determine[ing] which rules we can trust and which are wolves in sheep's clothing". Such principles facilitates one's own meta-practice, balancing "empiricism rigor and repeatability" against "inspiration, wonder and motivation", enabling the practitioner to develop the most effective approach to take for various life endeavors.

"The Key" introduces a series of tools or skills that can be brought to bear on the themes of this book. They include Agile Development, Theory of Constraints, Systems Thinking, Lateral Thinking and Neuro-Linguistic Programming, metaphor, refinement and pattern recognition amongst others. The author then shows how they relate to discovering the deep structures of problems and how they can be combined to support principles and practice. I found myself more familiar with some of these than others, however this chapter provided a good introduction to these techniques and their applicability, as well as providing many references to enable further study.

The chapter "Inspiration" concerns the motivation or desire to achieve on a personal level and, in particular, inspiring others. Here, the author rather cheekily turns the title of the volume around from "Working Life" to "A Life That Works" and goes on to explain that to inspire or be inspired you must place work into the context of that which gives one's life meaning. He draws the distinction between inspiration (as a principle) and motivation (as a process), going on to discuss management styles involving counterproductive attempts to motivate and inappropriate introduction of competition. This chapter also covers the introduction of change into an organization or team — particularly in the sense of changing context, methodology or practice — and mechanisms for avoiding conflict and inspiring others to embrace the change.

The longest chapter in the book is entitled "Balance" and discusses finding the inspired and effective centre or "norm" of your life, your team, your project etc. and staying there in the face of change. It is a rather long and rambling chapter and I think the book would have been better served by breaking it up into more digestible chunks. It is, however, where the previous threads coalesce, the author bringing them together with case studies and lengthy examples. He starts this chapter with the metaphor of life as a high wire balancing act with the processes we employ as the balancing pole. He then discusses the different feedback sensitivities and reactions required to regain the centre of balance as it shifts. The author gives as examples: the tensions between software stability and responsiveness to changing requirements, productivity and fatigue, skill and process, priority and effort, importance and urgency, and complexity and difficulty — all of which may need to be balanced against one another. He then covers in more detail issues surrounding the prioritizing of work activities and their impact on stress using a common importance/urgency quadrant model. This is followed by a description of strategies for negotiating this area. The author then touches upon the need to balance the requirement for skills, tools and processes at both a team and at a personal level, noting how to avoid potential conflict between personal career objectives and organizational goals.

The core of this chapter is based on a discussion of fulcrums, levers, balance and counterbalance as a metaphor for understanding where to apply effort in order to bring about change. This metaphor leads to a suggested mechanism for bringing the domain under analysis — whether your life, a project, or an organization — into balance. This follows on to a case study of the common situation regarding the competing needs of an organization's commercial, software development and production support groups which the author terms "The Consultant's Conundrum". This part of the chapter concludes with a fairly detailed approach to dealing with the seemingly disparate perceptions, aspirations and needs of these groups and bringing them into accord. It points out the role of management in this exercise and concludes that, like good jazz, the best of people in any discipline is born from an environment of controlled freedom.

The last main chapter "Context" rounds off the foregoing by introducing the concept of hierarchies of focus, the ability to move between the gestalt and the detail, and the pitfalls, challenges and mechanisms for success when doing so. The author entreats us to always know where are in the hierarchy of concerns and points out that many "arguments about the details" are due to fuzzy understanding of the higher layers of the problem at hand. A large portion of this chapter will be familiar to software developers as it uses metaphors drawn from object-oriented programming to describe problem analysis, the interactions between processes, and the relationship between organizational hierarchies and groups. This analysis of organization design leads into recommendations for those in a position to influence organizational structure. The chapter concludes with a discussion regarding project planning and process refactoring — and the various techniques that may be employed to inform these processes at various levels of a hierarchy of focus. I found this last part of immense value and the most important part of this chapter.

By the end of this volume, it is apparent that the author has much to say and is at times overeager to get it all out — bubbling over with ideas and metaphors. I found this volume somewhat unconventional in it's layout and writing style, but compelling and challenging nonetheless. It is the sort of book that lends itself to taking place on a professional 's bookshelf to be read and re-read over time — each reading yielding some nugget or insight overlooked in the past. I am certainly looking forward to the subsequent volumes and would recommend this series to anyone engaged in or with the IT industry.

You can purchase The Trousers of Reality - Volume 1: Working Life from Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.


This discussion has been archived. No new comments can be posted.

The Trousers of Reality

Comments Filter:
  • Indeed (Score:1, Insightful)

    by Anonymous Coward

    The Trousers of Reality -- Volume 1, Working Life is indeed a book about finding balance and satisfaction in life work and play

    Thanks for, uh, confirming my suspicions?

  • by stevens ( 84346 ) on Monday January 04, 2010 @02:53PM (#30644186) Homepage

    If the book is half as impenetrable as the review, I don't think it's for me.

    • If the book is half as impenetrable as the review, I don't think it's for me.

      Due to my lack of mod points, I can only add "I agree". After two paragraphs, I found myself skimming, after five I skipped straight to the comments.

    • Re: (Score:3, Funny)

      by hondo77 ( 324058 )
      +1 Read my mind
    • by elrous0 ( 869638 ) *
      When I was in grad school, I had a class where we had to critique each others' papers. One of the best criticisms I ever heard in that class was aimed at a particularly pompous bullshit artist: "I have never read so many words that said so little."
      • Re: (Score:3, Interesting)

        by epine ( 68316 )

        About the haystack I have yet to frisk:

        He can compress the most words into the smallest idea of any man I ever met.
                  — Abraham Lincoln (about a lawyer colleague)

        About the book's title:

        This was one of those points where the Trousers of Time bifurcated themselves, and if you weren't careful, you'd go down the wrong leg—
                  —Terry Pratchett in Guards! Guards!

    • [] []

      Those movies are a complete waste of time. The chick flicks from hell. Probably still more worthwhile than this book.

    • You post was impenetrable, I got lost at "half" so I gave it no mod points.
  • by PPH ( 736903 ) on Monday January 04, 2010 @02:56PM (#30644230)
    I find that in most of my life's pursuits, I derive maximum satisfaction when I leave both reality and my trousers at home.
    • Indeed! Needs ultimately are products of wants. You need to eat because you want to live. You need a job because you want to be financially capable. You need beer because you want to tune the bitch out...
    • "I reject your reality and substitute my pants"?

  • by vlm ( 69642 ) on Monday January 04, 2010 @02:58PM (#30644246)

    1) Is it a "business" book written using technical terms, or a "technical" book trying to sell into the business (or philosophical textbook?) arena? What is the educational level of the text? Whom is the books audience?

    2) How can a book with trousers in the title not result in any comments about hot grits for several minutes after posting?

    • by TheCarp ( 96830 )

      1. I could see a lot of overlap in those categories. Overall, it sounds like another book on how to live your life and be happy. Its a pretty big market. People have been trying their hand at books to do this since before the suggestions were based on following around the son of a carpenter. Of course, these days we have the Internet and so authors have to at least put in lots of confusing end notes if they want to make really outrageous claims.

      2. or Natalie Portman.


      • by vlm ( 69642 )

        1. I could see a lot of overlap in those categories.

        Yeah lots of overlap, but the best way to separate them would be to contrast two of Richard Feynman's classics. The "lectures on physics" is a very technical physics class, theoretically for all college freshmen, at least back in the old days when they were smarter, on average. On the other hand, "What Do You Care What Other People Think?" was freaking hilarious general read, that also got into some technical topics about the Challenger disaster as kind of a side story, but it was mostly about him getting

    • It's a dessert topping and a floor wax!
  • I thought them was biking shorts!
  • ...the Underpants of Destiny
  • trousers of reality? lol
  • About time the Theory of Constraints gets some play in IT.

  • ...or the review past the first paragraph and little table. This is slashdot right? Title, Author, Pages, Publisher, Rating, Reviewer, ISBN, Summary. Why isn't "License" on there? And if you suspect that, "The reason is obvious, because it is the same as all other dead-tree-book licenses" I still think it should be mentioned if only to pressure more authors to consider their audience when making decisions about licensing their content. If we can get details about the terms of the publishing contract e

    • Re: (Score:3, Informative)

      by vlm ( 69642 )

      I'd like to know where an author stands in the copyright debate, and this can be demonstrated by how they license the content they produce.

      If we are to shun musicians who cling to the RIAA, shouldn't we at least grumble at authors who cling to the old school book publishing establishment (I'm not even sure if there is a similar organization in book publishing) ?

      You didn't try very hard... I checked out the publishers web page, and oddly enough its about six pages and they only seem to publish three books. On the good side, they have a free preview online book reader thing, bad side its in flash (why not just text). On the bad side, about the third page or so of the free ebook preview is the usual dead tree title page "all rights reserved" legalese, so its not CC. Odd that a "software dude" would go all closed source. Also their six page website has a ridiculou

      • by schlick ( 73861 )

        You didn't try very hard...

        I didn't try at all, and that was my point. This being slashdot, that information should be in the header with all the other stuff I listed. I shouldn't have to go to the publishers website to find it out if it is "all rights reserved" or CC or what ever.

        • by vlm ( 69642 )

          This being slashdot, that information should be in the header with all the other stuff I listed. I shouldn't have to go to the publishers website to find it out if it is "all rights reserved" or CC or what ever.

          Fair enough. In most technical book reviews I complain that slashdot reviews should explain why I'd want to buy the book, if its just a slightly edited collection of last years google search results and some man pages from the old version, or what makes it better than that. Obviously not a problem with this book, but usually is a problem with the technical books.

          The slashdot book review guidelines need some modernization...


    • I'd like to know where an author stands in the copyright debate

      have you ever heard the phrase "monomania"?

      • by schlick ( 73861 )

        So I'm a monomaniac because I want to make an informed decision about who I give money to?

  • You don't need trousers or pants if you wear a kilt! :-)

    Can anybody explain why women love it when you wear a kilt? I mean the attention is really pleasant you know and there's always the obvious easy flirty line to be had in the conversation very early on, but slashdot girls, can you enlighten me?

    • by Bovius ( 1243040 )

      I'm fighting very, very hard to avoid some joke about how nobody has answered this post, because the reality is that it's that exact kind of joke that makes women not want to identify themselves here.

      So, ladies of slashdot: You're awesome, and I think it's awesome that you make up a significant part of our community. Thanks for putting up with the men.

  • There are three reviews of the book on Amazon. Shockingly, they all give the book five stars and are the only reviews posted on Amazon by the reviewers. The book sounds interesting, but I'd like to hear from someone who isn't the author's drinking buddy.
    • To be fair, one of the three Amazon reviewers admits being a friend on the author's. One can only assume the other two are as well. I wonder if they even read the book as both reviews read like back page blurb and mention opening minds...
  • Everyone in upper management where I used to work. Just the subtitle -- "Why Principles Are More Important Than Process" -- will send them right over the edge. They wouldn't do anything without some process being defined to control how everyone would accomplish it. "Process" was their life and they can't imagine anything happening without it. It was their ultimate mechanism for killing innovation in IT.
  • ... but soon you realize that the book is written somewhat fractally. Concepts are stated, revisited and linked with others into a whole, adding details as the iterations progress.

    So what you're saying is that it's a disorganized mess? No, that's wrong... It just looks like a disorganized mess - when you finally realize the subtle formula that underlies the whole, in the end, it's just random. Yeah - that's something I'd want to read.

  • Those are the wrong trousers [], Gromit!

  • Commenting on old slashdot article....

    My new for 2010 mantra - if I can't read the book on a modern eBook reader (kindle/nook/etc) or their pc/ipod/iphone/blackberry software equivalent, then I'm not buying... It's time the publishers and authors worked all that out and moved on to the 21st century...

Each new user of a new system uncovers a new class of bugs. -- Kernighan