I’m sort of alarmed how accurate it is.
I even played with Arch, Debian and went through college with a MacBook pro.
woah holy shit a bio?
I’m sort of alarmed how accurate it is.
I even played with Arch, Debian and went through college with a MacBook pro.
I fucking love Saddam Hussein’s Hiding Place.
You really never know where it will pop up next.
Our man-hours come from leadership and architects so separated from code they can’t agree on drawings or what constitutes a micro service architecture or… Any real pattern at all.
Something I don’t get paid enough to understand - what constitutes contributions, and what’s the definition of selling the software?
For instance, I don’t think I’ve worked on a project where we have made changes to the source code for security policies (much quicker path to update immediately if something gets flagged). But I don’t think I know of an instance where we sell our software as a service - as far as I know it’s largely used to support other services we sell.
Except now that I say that, that’s not entirely true, we DO have a review board that we have to submit every third party library to and it takes forever to hear back but we have occasionally gotten a “no can’t use that” or “contract is pending.” So maybe I’m just super unaware of who reviews the third party software and they review the licenses.
try finger, penguin?
Fair. Thanks for that counterpoint.
Yes. And time.
We make a lot more money by testing in production, and let the users tell us what’s wrong. It’s much faster.
That’s… Not great. I didn’t actually think about what all these wild AV systems could do, but that’s incredibly broad access.
Maybe I’m just old, but it always strikes me as odd that you’d spend so much money on that much intrusive power that on a good day slows your machines down and on a bad day this happens.
I get that Users are stupid. But maybe you shouldn’t let users install anything. And maybe your machines shouldn’t have access to things that can give them malware. Some times, you don’t need everything connected to a network.
That’s the impressive part of all this. Microsoft didn’t do it. CloudStrike did it.
Microsoft left something in a state that allowed CloudStrike to fuck up enough to brick systems.
It’s why we spend a lot of time reviewing security analysis of our own software - if there’s a way to fuck everything up, it better not because we enabled it to get fucked.
we really need to stop calling it formerly Twitter and just call it Shitter.
he ruined the platform, the people can ruin a name
Well. I mean, that’s pretty cool. I don’t think I would have ever guess that was an actual function from systemd but here we are