Comment by nurettin
16 hours ago
This is why I prefer clunky hardware with heating cpus and a slow disk. You can easily feel that you wrote bad code from audio and tactile feedback.
16 hours ago
This is why I prefer clunky hardware with heating cpus and a slow disk. You can easily feel that you wrote bad code from audio and tactile feedback.
I’ve heard of people doing ambient performance profiling by instrumenting their code to insert clicks into an audio buffer based on a high precision clock and piping it out a speaker. You get to learn the sound of your code at 44.1KHz
This might be the most absurdly terrific thing I’ve read in a while - like a profiler equivalent of a Geiger counter.
We did something like that for a hiring project once:
https://github.com/tonarino/acoustic_profiler
*vibe coding sounds* "3.6 roentgen. not great, not terrible"