The Information Paradox

Almost every IT shop has a methodology. Where I'm currently working, they're using Macroscope which, from what I see in the IT market in Montreal, has been in good use around many places here for two decades (I even studied one of its ancestors in College in 1994)

Fujitsu is now in charge of that methodology, and they offer for free an electronic version of a book named The Information Paradox which, I thought, could have helped me understand better that methodology.

I was dead wrong. I tried reading the first two chapters and couldn't finish a paragraph without phasing out and thinking about, oh, various subjects such as home improvement, Star Trek, Bangladesh or Yonge Street. Yep, that's right, a technical guy like me just cannot read this book and remain sane. It's all talk about IT Portfolio, governance, and some other nonsense which doesn't ring a bell. But who actually reads this book? Lots of people, it seems, and I figure they're all working for what I used to call the IT Gestapo. Now that I jumped the barrier to architecture, they're supposed to be my friends now. Yet this friendship is only on paper; I think I'll never be able to share a beer with such people who would talk about IT portfolio the same way I talk about, say, the latest FreeBSD release.

So it looks like with a B.Sc., I'm not qualified to read that damn book. And it's fair game: people with B.A.'s could probably never understand why APUE is one of my favorite books.

O.