When your code works but no idea how
@stux Let me test it so I can find a bug which you then have to fix after which the code won't work anymore 😇
@stux Been there, done that, got the T-shirt, wore it to shreds. 

@stux For some reason it makes me think of this comparison of APL to shooting yourself in the foot: "You hear a gunshot and there's a hole in your foot, but you don't remember enough linear algebra to understand what happened.".

http://www.toodarkpark.org/computers/humor/shoot-self-in-foot.html

Shooting yourself in the foot in various programming languages

@mrbruno @stux @rdm

HyperTalk
[…] we anticipate this functionality to be incorporated into the next major release.

😢

@Charles Yes! Vaporware!! Score!

@mrbruno

I loved this. Thanks for sharing it!

@stux

@stux

Amazed at the effort it probably took to make that train work that way so please don't tell me it's AI.

@the5thColumnist @stux The way it probably works is that, after going off the tracks, the model train hits the wall at an angle, and turns so that it goes parallel to the wall. Then the track was positioned so the model train got back on it.

@bzdev @stux

My assumption too but I expect there is a lot of trial and error to get all the positioning correct.

@the5thColumnist @bzdev @stux yes some experimentation, but I think it doesn't have to be too precise. The angle to hit the wall must be somewhat shallow, the stretch along the wall perhaps a trains length, and then stabilize/tape the rail down where the train hops back on. This is very cool. Sadly I've been in too many developments like this.
@stux the test passes, but the product doesn’t because it relies on environmental conditions that aren’t necessarily documented.

@c0dec0dec0de @stux as a quality control guy, "it worked once, ship it" is not a standard I want to approve.

Me (mostly in my head): "Maybe if you took your torque training seriously, and didn't let your team break so many parts, you wouldn't be behind on your commits."

@Urban_Hermit @c0dec0dec0de @stux
Something like this happened at our company.
Tested one of our standard machines, yup pass. Once at the customer, the heater coil burns out immediately. We're in Europe, customer is in Australia, Murphy's law. Weeks later, coil arrives, service guy installs it. The thing burns out right away. Customer is royally pissed off, rightly so. They said we could have burnt down their facility with the faulty device.
(1/2)
@Urban_Hermit @c0dec0dec0de @stux
Turns out production accidentally reversed the connection for the heater coil, meaning it was under tension by default.
QC just tested: does it heat? Yup coil is hot. Does it cool? Yup valve opens.
We changed our protocols after that.
(2/2)
@stux @Viss Just because it's Undefined Behavior doesn't mean it won't work, right? 
@catsalad @stux let the bits flip where they may :D
@stux "Works fine in DEV and TST. Can't replicate customer's reported defect. Closing "
@stux I can't stop looking to see if it works every time.
@stux I did that in the past.
@stux side-effect driven development 👌

@stux

AI generator would never be able to do THAT 😆

That takes hours of coffee ROTFLMAO

@stux I never know which is worse - when code works even when you know it's completely wrong, or when it doesn't but you can't figure out why...
@stuartb @stux definition of the word "worse" is unclear. But it's usually the former that fails to keep me up at night less often.
@stux Deutsche Bahn #DB_Bahn Zulaufstrecke Brenner Basistunnel

@stux

Wow!

It’s the physics… (and the tweaked parameters I guess…).

@stux
If the wall is your system architecture, i think most programs in the 80's probably worked this way
@stux It's a feature! It's a wall controller setup. The product is so flexible that allows such config.
@stux
The programmers' lament 😥

@AlisonW @stux

Correction:

"It doesn't work .... meh"
"It works .... meh"

@AlisonW @stux

Fixing a problem and not knowing why is sometimes worse that not being able to fix it.

@VulcanTourist @stux
Absolutely. If I don't know _why_ then I can't repeat the steps if it happens again.
@stux my code talking to that one closed source library.
@stux Works perfectly on my machine.

@sir_toootenstein

I've always loved the magic in that phrase

@stux

@stux
Oh gods below, I've been there.
@stux And waste time trying to understand it, and break it later. 😅😅😅😅
@stux jajjajjajajajajjajajjaja
@stux Somebody vibed that sucker right up!
@stux Use after free or buffer overrun into and out of uninitialized memory? 

@stux

You can learn a lot about an individual
just by reading through his code,
even in hexadecimal.
Mel was, I think, an unsung genius.

Perhaps my greatest shock came
when I found an innocent loop that had no test in it.
No test. *None*.
Common sense said it had to be a closed loop,
where the program would circle, forever, endlessly.
Program control passed right through it, however,
and safely out the other side.
It took me two weeks to figure it out.

@xenotrope @stux And you added comments, or even changed the code, to make it clearer to those who follow you in maintaining it, yes?

@PatternChaser @stux

I was impressed enough that I quit looking for the
offending test,
telling the Big Boss I couldn't find it.
He didn't seem surprised.

https://users.cs.utah.edu/~elb/folklore/mel.html

The Story of Mel

@stux

C'est qu'il y a quand même un bug mais qu'il ne plante pas assé le programme pour donner quand même l'impression qu'il fonctionne.

Ca m'est arrivé ... c'est la pire des choses. 🤣

@stux

I thought that "hitting the wall" was a bad thing 🤔

@lnlyisol @stux This what we in the business like to call 'Expected Behavior'.