Writing a book about software engineering, what do you want in it?

Is there some magical way to avoid fixing pdf parsing code every 2-3 months when ever something small changes? And where the list of small things that change is quite large and random. It has become a full time job for some people I work with - decoding corporate/govt pdfs. They could be spending their time on more useful stuff instead of header format changed, data format changed, location moved etc etc so parser crashed.

Hey all,

I want to write a book about software engineering, but I want to make it applicable for people. So I've put up the above survey so that people can share some of their thoughts and experiences.

Please feel free to fill in the questionnaire or write some comments below if you have some ideas on what you're looking for.