I just finished reading it. Even though it's tongue in cheek humorous in some places, it's a must read for anyone who deals with systems (programmers/engineers

I just finished reading it. Even though it's tongue in cheek humorous in some places, it's a must read for anyone who deals with systems (programmers/engineers/politicos/the average citizen). One of the hardest things for a programmer to do is to NOT build a system. But sometimes (everytime?) the avoidance of a system (if possible) is the best option. An example: Our company just implemented a huge ERP system from a well known vendor. As expected the problems we were trying to solve (resource management, etc) became secondary to keeping the system up and running. The system itself becomes the problem.