Software gore is when software acts outside its parameters and malfunctions unpredictable. Software gore cannot be intentional, and it must not be a fault of the design (crappy design).
Asshole design - deliberately bad software (not software gore)
Crappy design - Issues caused by poor design (not software gore)
Is the issue here to do with design? Is the issue intentional? Does the actual issue tell you what's wrong? Is the issue caused by something other than software?
If the answer on all those questions is no, congratulations you probably got software gore!
Mokou on August 21st, 2018 at 11:14 UTC »
I remember being taught to program with little robots in university that operated a lot like this. We had to write code to allow them to travel an arbitrary walled path without running into this exact issue.
As I recall, my solution was the far from elegant "move back a little, turn a random number of degrees away from the triggered sensor and try to move forward again". It was potentially very slow, but it always got there.
FrAX_ on August 21st, 2018 at 10:23 UTC »
If (question.Asked) { answer.Correctly; }
AI is easy
drdrero on August 21st, 2018 at 09:05 UTC »
I was doing work when my robot got stuck in an endless loop trying to clean the corner. I stopped filming but the robo kept going for another minute. Then i repositioned it and it went straight back to corner, as if it was trying to end its life.
Robots will definitely take over the world soon.