haha no source, just a dumb joke.

Japan: Checkmate

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

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

Full name is GNUIMP anyway

Exactly! You actually CAN have 50 people finish something 50x faster, but it takes a shitload of planning, and that equals time and money no company I have ever worked for, or even known of, would allocate to something that isn’t generating immediate income.

Take the Hoover Dam for example: Dsigned over 3 ish years and built in 5, at a time when nothing that huge had ever been made before, at less than a billion in today money, and 2 years ahead of schedule. It’s 90 years old.

JavaScript: :wide eyed and smiling: Sure why not! You’re the boss!

Python: Sighing and downing half a bottle of Advil: Sure. Why not, you’re the boss.

The scripting language formerly known as Java.

Tabs are a dark pattern confirmed.

The war is over, long live spaces.

I’m going to rename my NAS “online discussions” in your honor.

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)

That’s why the cat is smug. It knows you know this.

Distributed Honor-system Clothes Peg Server

I am very confused by your comment. Are you saying Putin never said that, or are you saying he was lying?

From Putin’s actual mouth:

ON DECISION TO LAUNCH ‘SPECIAL MILITARY OPERATION’

“We saw military infrastructure being ramped up, hundreds of military advisers working and regular deliveries of modern weapons from NATO. (The level of) danger was increasing every day. Russia preventively rebuffed the aggressor. It was necessary, timely and … right. The decision of a sovereign, strong, independent country.”

Just to be clear, he definitely said that, but he was definitely lying.

(source: https://www.reuters.com/world/europe/putin-speaks-victory-day-parade-moscows-red-square-2022-05-09/)

The opposite. In the face of humiliation, the world worries about Putin launching nukes. A no-name lackey that lucks into the spot after Putin gets defenestrated would double down, not pull back. They would redouble their efforts to appear strong because they feel vulnerable.

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.

They should merge with RadioShack and that company that rented DVD’s out of ATM’s in front of gas stations.

Claude told him to be confident

You know how you close your eyes when you’re trying to listen to something carefully? There you go.