Most software programming take the form of “if it’s fixed, we’re not going to break it”. Any time you change code, you run the risk of introducing a new bug. That’s why towards the end of software projects, bugs that are found will NOT get fixed if the user impact is trivial (”User must stand on head and type under a full moon while chanting verses from the Necronomicon to get this display issue in this dialog to show, it doesn’t crash or cause data destruction, and we’d need to do three week’s worth of retesting if we make any changes. We’re not fixing this 3 days before we release. We can get this on the next release.”).

Do teams do stuff like refactoring or other Good Things? Sometimes, if they have the time and there’s good reasons to do it. But again…every time you touch working code, you run a risk of breaking it. So anyone who does commercial software development on a large project doesn’t just do this for fun, or for some desire for arbitrary code purity.

It looks like there is very annoying bug in the print API used by MS Word. This bugs happens when customer print a document with section break that were inserted to allow them to change page orientation within the same document.

As you know, this force Word to print separate document, and creates to our customer many problems from:
- not being able to use 2 side printing properly, nor staples from their printers
- not being able to create PDF

This you are working on fixing some stuff for leaopard, could you take a look at this!

Thanks

Oh, and BTW, could you ask Steve to just buy out Thrusby and bundle dave and AdmitMac within the OS. This will so much simplify the life of our commun corporate customer pledge with SMB problems/limits of the standard MacOS functions