\n'; msg += ' Real-time - For the purposes of this '; msg += 'discussion the difference between real-time and not '; msg += 'real-time are almost exactly analogous to the difference '; msg += 'between instant messaging and forum messaging. '; msg += 'Instant messaging or verbal discussion are real-time, '; msg += 'requiring participants to occupy the same point in time '; msg += 'in order to exchange information. On the other hand forum '; msg += 'messaging or written plans are outside of real time, '; msg += 'freeing all participants to read and comment on the '; msg += 'information at whatever time is most convenient for them. '; HPopNF('Note #1', msg); } function FN02() { var msg = ''; msg = 'Note 2
\n'; msg += ' Stack interactions with recursion - '; msg += 'On some projects I\'ve done, the same people who pepper '; msg += 'the code with pointer bombs were also likely to make '; msg += 'mistakes with recursion that blow up the stack. These '; msg += 'have much the same effect on code stability as pointer '; msg += 'mistakes in that the code will seem to run just fine for '; msg += 'a couple of hours or even a couple of days before '; msg += 'crashing (usually just long enough to do a demo for the '; msg += 'executives). But the odds will "usually" catch '; msg += 'up and it will crash.
Unlike pointer bombs, these are '; msg += 'difficult to find with a simple code review and don\'t '; msg += 'lend themselves to using the debugger or other '; msg += 'automation. They usually involve un-rewound recursion '; msg += 'that is spread over three or more functions (often dipping '; msg += 'down into system calls). A weak '; msg += 'indicator that this might be happening is if you see '; msg += 'large stack size settings as part of the make. That is often '; msg += 'called for, but it could also be an indicator that people '; msg += 'are tweaking around the edges in order to get the project '; msg += 'through meeting demonstrations without crashing.'; HPopNF('Note #2', msg); } function FN03() { var msg = ''; msg = 'Note 3
\n' msg += ' Specific mechanisms - If you\'re '; msg += ' going to formally allow programmers to limit access, '; msg += ' giving them time for which they have nearly complete '; msg += ' control over interruptions, then it might also be wise to '; msg += ' specifically set aside some times when they can '; msg += ' be interrupted. Doing this will coordinate those times, '; msg += ' mainly so that interruptible time occurs at the same time '; msg += ' for everyone. Formally planning common, synchronized '; msg += ' times when all are free to interrupt others may also help '; msg += ' protect and strengthen their ability to limit '; msg += ' interruptions during Do-Not-Disturb time.'; HPopNF('Note #3', msg); }