A shitty Belkin KVM in certain configurations can allow this to happen.
There's a bug which keeps generating chr(32) characters when you activate the keyboard shortcut (scroll lock twice), and try to switch to another machine.
It will keep pumping out those spaces on whatever fields was selected at the time, so if you take your time before you switch back, you are going to be in for a lot of fun.
Haven't read the link yet, but wanted to share this sooner than later.
If you're in a codebase composed largely of side-effect free functions or well encapsulated Object Oriented code, it's a very good way to debug. I had great success with such debugging and even coding and new development in Smalltalk environments for over a decade.
On the other hand, if your codebase is full of side effects and doesn't have good encapsulation (perhaps there's a lot of fiddling with globals) then you're going to have a bad time. But to me this isn't because the debugging method is bad. To me, it's because your codebase is designed with lots of tight coupling and side effects. You have an architecture that makes it harder to reason, debug, and refactor your code. This isn't just spouting. I'm basing this on many years of experience. And yes, I saw both kinds of Smalltalk code, and the effect is exactly as I described. Guess which codebases were more productive?
Thus Personnel became Human Resources.
But often the new words are, with the passage of time, clearly just as, or more offensive than their predecessors. I mean, "Human Resources"?!! WTF! Are people really just "resources"? To me, Personnel sounds way friendlier.
Another one is around disability. We would never describe someone today as retarded. Yet really, is disabled any better? I'd rather be retarded (as in, slowed down a little) than disabled (completely stopped).
[close to my heart: we write HR software :)]
I know this is really-really hard to accomplish, but some IDEs do it.
The only thing that's "optional" and a little over the top (but very useful) is time-travel debugging.
How come the open source world hasn't been able to create a debugger that's as good as the (still primitive) debugger in Visual Studio 6.0? It's astonishing to me how bad the state of the art is.
What's your take on this thought experiment:
Imagine a giant barrel of apples on the side of the road with a coffee can next to it. There's a sign that says "Take an Apple, Leave a Penny"
Now imagine you don't carry pennies for moral and/or pragmatic reasons. They're too heavy, or you don't want to support Big Copper, whatever. But you want an apple.
Do you take one?
Let's do a realistic thought experiment that's actually fair:
Imagine you have a movie that you love. It's showing tonight on an over-the-air channel that inserts ads throughout it. You decide to record the show and watch it later.
Do you skip the ads?