You're viewing a single thread.
It's me. I write software and complain to the hardware team when I don't have leds to blink for diagnostic purposes.
Exactly…..
Like, do you not want a light that informs you of the evil?
Just because I installed a check-engine light in my AI doesn’t mean I designed it to be evil 😝
I can see the regulation now. All robots MUST have red eye error indicators. They must glow for 3 seconds on every boot to verify they are in working order.
Reboot
1
2
3
4?! Fuck!RUN
OH SHI-
I feel like this just opens up a whole new line of inquiries.
For starters, how did you define "evil" and how complicated was it to design its detection? Is there an acceptable amount of evil that they can do, as a treat?
Hillary: robots must follow the three laws of robotics
Bernie: robots can have a little evil
Bernie would never allow robots to be evil, but he would allow them a little salami.
Trump: The three laws of robotics are woke and destroying this country
All my homies love diagnosing problems by decoding LEDs blinking in code.
I write code for embedded systems that have hard real-time deadlines. Flashing an LED is an inexpensive number of operations compared to most other diagnostic techniques. I can connect an oscilloscope to them to get meaningful accurate time measurements. I am not blinking out Morse code status messages (although I have considered it for some particularly squirrelly problems).
Take to another level by attaching a speaker to a PWM peripheral, now you can debug by ear, whilst driving your colleagues barmy with the beeps. The only tricky bit is working out if it was three beeps and a boop, or two beeps then a beep-boop.
More fun to vary the pitch and length of the beep rather than the number of beeps.