For me, the programming equivalent of the blue light is my development environment being in focus, and receiving key strokes and mouse clicks. Crude but surpri

For me, the programming equivalent of the blue light is my development environment being in focus, and receiving key strokes and mouse clicks. Crude but surprisingly accurate. If I am not interacting with my development environment, it usually mean there is a problem somewhere. Sometimes that's me (slacking off, getting lost,...), sometimes it is organisational (useless meetings and processes,...), sometimes technical (slow computer, unresponsive network,...). But it is always a sign of inefficiency.