> I think books on software management and process are mostly lost on someone who hasn't been involved in the process. I think that's true and fair. However, o

> I think books on software management and process are mostly lost on someone who hasn't been involved in the process. I think that's true and fair. However, once some experience has been acquired, I believe it's helpful to evaluate whether it's good experience or bad experience. Comparisons against the literature can be helpful at that point. Case in point: I tried reading 'The Psychology of Computer Programming' in college, but it didn't make much sense to me. Coming to it 15 years later, I realize it'd have been the perfect companion to my first five years in industry, naming and describing problems I'd faced and solutions that only came through experience more painful than reading.