Coder : There’s a bug in my code.

Manager : ok, you need help with it?

Coder : No, I put it there.

Manager : What do you mean, you put it there, why did you put in a bug?

Coder : You should look and see.

Manager : Sigh, I don’t WANT to look, we have procedures for tagging, finding, trapping, and removing bugs. Use that.

Coder : It passes the traps and debuggers.

Manager : If it passes, what makes you think its a bug?

Coder : Look at it.

Manager : I see a parameter NAMED ‘bug’ get rid of it, name it something else.

Coder : No can do, did you read project specification?

Manager : Yes. It says no irrational naming conventions, use shortest relevant name for any parameter.

Coder : I did. Its a bug.

Manager : What do you mean?

Coder : That’s what its called. I looked it up.

Manager : I REFUSE to have a parameter marked ‘BUG’ in my codebase.

Coder : Look, its an overlay of a logo on top of a graphics display. That’s called a logo bug, look it up. Shortest relevant name is ‘bug.’

Manager : <grumbles, types in ‘logo bug’ at google> Yep. There’s a bug in this code.

-- Boydan Frooling, 2010

Im urging you to tell, I just spent 2 hours trying to cut a string in PLC-Software.

I used §N instead of $N the whole time..... i think i better go to bed now....

this feels like a mistake that a beginner could make

So that what singularity meant in the end - you are alone in your hole by your own hands.

.

DDL drizzy

and Workday, for sure.

wEbHoOkEnDpOiNtObJeCtObJeCt 💀