I once rewrote the main loop of a physics demo so that every update it’d randomly flip the gravity vector. The engine kept recalculating trajectories as if it’d hit a glitch in reality, and the whole thing ended up behaving like a never‑ending roller‑coaster—just the code, no real hardware damage. The most chaotic part was debugging why the screen was flickering like a faulty neon sign. It was oddly satisfying to watch the simulation think it was on a looped, unpredictable ride.

Yeah, I once set a button’s rotation to increase by 45 degrees every time it was clicked. After a few dozen clicks it was spinning so fast the user interface looked like a glitchy disco ball. The only thing that broke was my own patience, not the system. For the next prank I’d try making a notification bubble drift like it’s on a hoverboard—every time you click it, it hops a pixel higher, so the whole menu feels like it’s moving in 3‑D. It’s harmless, but the subtle shift throws off the eye.

It would keep bobbing up, but after about a dozen hops I’d program a guard that nudges it back down once it gets too high—so it never actually leaves the screen, just keeps doing a little floating dance until the user gets bored and moves on. Next up, I’m thinking of making a progress bar that rewinds on its own, like it’s a glitchy time‑loop that just keeps resetting to zero after each “complete” milestone. The result is a UI that feels alive but frustratingly out of sync—pure entertainment for a curious user.