I’m currently in a production support role in the US, and I’d never consider it: I work too closely with production operatives that they’d smell it on me. My last couple of role involved programming automated forklifts, so it was strictly forbidden.

Ten years ago I was doing an internship an engineering firm in the UK, and a few times we went out for a beer with lunch. It wasn’t exactly common, but it did happen.

Them: Can you perform under pressure?

Me: Mmm num ba de
Dum bum ba be
Doo buh dum ba beh beh

As someone who used to troubleshoot an extremely complex system for my day job, I can say I’ve worked my way across the entire bell curve.

The things is, if you try to parse html with a regex, you will always be able to construct valid html that will break it, no matter how complex your regex becomes.

United. Twice. They damaged my luggage both times.

I’ve only flown Delta and American since then.

It’s definitely great in theory until you inherit a codebase with no tests, poor documentation, and numerous reported bugs already live in production. Even better if it was written by people hired because they could do other things better than they could code - which looking at some of the unlabeled wiring messes we were left, isn’t saying a lot.

I tried uploading a banner for a community I mod and was met by a JSON parser error message, so that’s not happening there until there have been a few more updates.

Did you know that XLR is also something of a standard for interchangeable sex machine attachments?

Excuse me, I believe you have my stapler?

There’s also !amateur_radio@lemmy.radio which is reasonably active.