It reminds me of Extreme Feedback Device (XFD) lava lamps, pilot lights, and more.
The best example of which being Retaliation - https://github.com/codedance/Retaliation
61–70 of 336 posts
It reminds me of Extreme Feedback Device (XFD) lava lamps, pilot lights, and more.
The best example of which being Retaliation - https://github.com/codedance/Retaliation
its 25 years later and the thought of having a single discoverable element on the net scares me.
i would really like an app that can create ambient music with composition: small songs that can overlay with harmony; if my network is running hot the baseline ramps up. if i have emails waiting, little tweets from a treble track that are fleeting but line up with the beat. there's so many ways i could use that soundtrack. plug it into the ide, errors in the buffer, subtle cues.
95% of my work (web dev) isn't so much waiting for something to happen, where a notification of any sort would be useful. Most builds etc only take a few seconds, so I just wait. Most of the work is thinking through a problem, then ensuring it's coded correctly. The colors and syntax highlighting and squiggly lines and Typescript warnings etc (in Jetbrains) are all helpful because they are contextual . "Hey, this fun…
Of course there are already onscreen solutions for that, such as indicators in the minimap, but it could be more obvious as a sound.
https://github.com/kristiandupont/react-geiger This plays a click when React components rerender, to make you aware of the page performance
I crafted a oneliner that `tail -f`'d the logs and played a note for each response. I believe there were different notes for different HTTP status codes but it was years ago so the details flee me.
`$ ... && say 'Notice me father, I am complete'` (something I add to longer scripts when the job gets particularly boring)
preemptively, to anyone telling me this is terrible, i'd say this is a toy and a subjective one, but that we're detailing our personal flows here, and not inventing interfaces :)
At a previous job we had a service that handled around 1 query per second. I crafted a oneliner that `tail -f`'d the logs and played a note for each response. I believe there were different notes for different HTTP status codes but it was years ago so the details flee me.