Surely it’s the rapid growth and massive profits that are the problem? Not a lack of energy infrastructure planning or regulation.

haha no source, just a dumb joke.

Abbot just creamed his chair and he doesn’t even know why.

Japan: Checkmate

:: Reveals 10X more laws regulating game consoles ::

I know, I know, it’s pronounced “Nyïmp”

Full name is GNUIMP anyway

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

I worked with dudes that smoked like it was a job requirement that looked haggard AF at 30. I didn’t recognize one of them 10 years later because he had stopped smoking and dropped a ton of weight - he looked 10 years younger than when I met him.

Smoking is bad, kids. And no, Vaping probably isn’t much better.

Well you see, testosterone levels rose when Regan was elected, 9/11 happened, and The Apprentice launched.

It’s basically science.

(this post was satire, and I’m sorry if it made anyone vomit)

Unsolicited fact: Heinz picked the number 57 at random, it just sounded like good marketing at a time when things were general marketed as “tonic #4” and the like.

(well, maybe not fact, more like probable truth)

Distributed Honor-system Clothes Peg Server

A repo dedicated to non-unit-test tests would be the best way to go. No need to pollute your main code repo with orders of magnitude more code and junk than the actual application.

That said, from what I understand of the exploit, it could have been avoided by having packaging and testing run in different environments (I could be wrong here, I’ve only given the explanation a cursory look). The tests modified the code that got released. Tests rightly shouldn’t be constrained by other demands (like specific versions of libraries that may be shared between the test and build steps, for example), and the deploy/build step shouldn’t have to work around whatever side effects the tests might create. Containers are easy to spin up.

Keeping them separate helps. Sure, you could do folders on the same repo, but test repos are usually huge compared to code repos (in my experience) and it’s nicer to work with a repo that keeps its focus tight.

It’s comically dumb to assume all tests are equal and should absolutely live in the same repo as the code they test, when writing tests that function multiple codebases is trivial, necessary, and ubiquitous.

I see a dark room of shady, hoody-wearing, code-projected-on-their-faces, typing-on-two-keyboards-at-once 90’s movie style hackers. The tables are littered with empty energy drink cans and empty pill bottles.

A man walks in. Smoking a thin cigarette, covered in tattoos and dressed in the flashiest interpretation of “Yakuza Gangster” imaginable, he grunts with disgust and mutters something in Japanese as he throws the cigarette to the floor, grinding it into the carpet with his thousand dollar shoes.

Flipping on the lights with an angry flourish, he yells at the room to gather for standup.

It’s not uncommon to keep example bad data around for regression to run against, and I imagine that’s not the only example in a compression library, but I’d definitely consider that a level of testing above unittests, and would not include it in the main repo. Tests that verify behavior at run time, either when interacting with the user, integrating with other software or services, or after being packaged, belong elsewhere. In summary, this is lazy.

Claude told him to be confident

I don’t like it, but I like it more than the old way of holding the button down to get to the menu. I do hate that the “see all” menu doesn’t just expand the current menu, it takes you to the old menu. There’s definitely hints of windows95 creeping into Android.

The P in Prod stands for “It’ll be Pfine”

10 minutes for a process is essentially infinity

I would likely start here:

https://raspberrytips.com/raspberry-pi-gpio-pins/

You’ll need some code running at startup as a daemon for monitoring the pins on the rpi, but once you have that, triggering literally whatever you want from the python script is one os.popen() away.

Spigen Tough Armor series. I’ve had one on my last three pixels, and they are the only three phones I haven’t destroyed.