I grew up writing my own games on the C64, and one of the fun things that always got me was how close the video RAM was to the memory containing your program itself.
So if you had a game where you moved a little character around the screen with the joystick, and you neglected to handle the case where he went off the screen to the top or bottom, you could crash him right into your source code (which was being actively interpreted).
It'd dump you out abruptly, you'd list your program and find that a section had been monched and now contained a bunch of random special characters. Ouch.
That hardly ever happens to me anymore, writing front-end code for the browser. But still I make a point of checking my bounds, just in case!
So if you had a game where you moved a little character around the screen with the joystick, and you neglected to handle the case where he went off the screen to the top or bottom, you could crash him right into your source code (which was being actively interpreted).
It'd dump you out abruptly, you'd list your program and find that a section had been monched and now contained a bunch of random special characters. Ouch.
That hardly ever happens to me anymore, writing front-end code for the browser. But still I make a point of checking my bounds, just in case!