Can’t even make out dialogue in my native language in a quiet room sometimes. Not just in action scenes, why are ambient sounds louder than the dialogue? 😤
It’s interesting what you get used to. My wife is from a country with a strong dubbing culture and where I’m from all foreign films were always subbed.
She finds the subtitles distracting, whereas I barely register them and read almost subconsciously.
Hmm, I’m not quite well read enough to understand this. I was thinking about running this in an LXC container, does the removal of non Docker setups mean that I would have to nest Docker in the LXC container? 😕
Me at a previous workplace.
-This is a piece of shit, who is the code owner of this module.
Ah, it’s me (“inheriting” code ownership when someone left was common)
Who did this change
Ah, it was me
Surely I just made a minor change to this line here, who wrote the function.
it was me, it was me all the way down
Fits the general theme of the thread as it was not giving any trouble for a year before being found.
TLDW;? Will watch it after work, but I’m curious now. 😁
Had to do a hard reset today. Quite annoying, but most things synced back automatically.
We use slack for some things and teams for some things at work. Can’t say I really prefer one over the other. My dream is if we could just decide on one platform so I can find shit. Any of them!
Same on boost
I think I need a little more help here. Maybe it’s just about not having English as a native language, but the link talks about avoiding the word bug because of connections to sodomy?
Honestly asking, who gave them horrible reviews? Have seen some middling ones and support has some negative threads in the forum, but nothing really bad?
45 year old here, I remember my father using cheques a long time ago. (non-USAian)
Read your comment, thought well that sucks and proceeded to do exactly the same 🤦♂️
Sounds like Ubuntu pro maybe?
That’s just for tax evasion
Upon changing ticket system at work, one of the graybeards asked about apis and cli access because “real men don’t click”
The crash early, crash often approach of Erlang has made for some amazingly resilient systems.
One time on a project I was working on, some horribly broken code was merged (nobody in the team had even heard of reviewing code). As soon as a specific call was made, it was executed once and then the thread crashed. The only way we noticed was that response times increased with load. All data and behavior was still correct. Whole nodes could go down and all you notice is a dip in performance until it comes back online.
Of course it requires special care in designing. Everything runs in stateless server threads with supervisors restarting them as needed. This in turn requires some language support, like lightweight threads. Our application would happily run tens of thousands of threads on an ancient sparkstation.