nxdefiant
joined 2 years ago
The north east US is dotted with high (physical) security Amazon data centers . I promise those aren't hosting files you can search Google for, if you know what I mean.
wtf just call in dead and tell them you'll see how alive you feel tomorrow.
Square wishing he was as famous as Phillips, sad.
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.
The worst part of it is most big companies are forcing RTO to either justify the leases they don't want to pay to break, or to satisfy tax incentives agreements they made with municipalities.
In both cases, they're deciding it's better if you pay - in time, gas, car maintenance, mental health, productivity, and stress - for their business decisions that went bad instead of paying money out of their own bloated pockets.
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.
I was gonna make a joke about a Palantir AI service and then I remembered Palantir is a real company now being run by Morgoth.