umm if ur talking windows that would be because microsoft fired like the entire testing department
in windows we are all now the testing department.
His name was Robert Paulsen
They outsourced it, just like Pfizer.
umm if ur talking windows that would be because microsoft fired like the entire testing department
in windows we are all now the testing department.
His name was Robert Paulsen
They outsourced it, just like Pfizer.
My iPhone did an update and got all fucky. It’s so aggravating. Do you want to update. No. Go to sleep, wake up, “we updated for you” FUCK YOU
You can turn off automatic updates. Which is good because updates never make anything better
Fucking retarded shitskin faggots just fuck everything up and have no place in White society.
The truth!
Most of the white programmers retired from the IRS. The IRS is being run by jews, niggers and they think shitskins can program. Call them now to get a status of your tax situation. They don't answer the phone anymore.
Would be funny if millions of people called in wondering where their $20k refund is.
If everyone filed a paper return it would cripple the IRS. When you E-file you give the government a ton of information that they don't collect from a paper return.
They call you now, get your gift cards ready.
True. I used to update asap, but now I never update unless I have to.
I know some skilled pajeets but holy shit the bad ones are common and are a nightmare to work with.
Where do these skilled Pajeets work that you speak of?
Tech companies duh
They clearly aren't at those companies. I've had to call for tech support enough times and I wouldn't consider them to be skilled.
I'm really tired of all the updates, I'm tired of the emails about the updates and I'm also tired of popups getting in my way on every UI.
I simply don't need to know or care about most of this shit.
Did you know...
I'm trying to do work, you cocksucker!
No it saves time and money to just have everyone else do your debugging and quality testing for you for free.
most devs just suck at what they do and are treated like God's gift. I've had to help them fix their shit for over a decade and apparently it's my fault that their code sucks.
When I was a network/sys admin in the early 00s, the secret to my success was I never fiddled with the servers or patched. Other than rebooting them every Friday evening, I just let them run and they ran.
When some Lebanese asshole took over my job, the systems were always down. He was one of those retards that installs every new patch as soon as it comes out.
People said, "when you were running things here, the servers were up for a whole year". I said, "yeah, I only patched like once a year".
Funny thing, how I got "laid off" was that the servers went down one day because he told me to reboot them while management was out and when they didn't come back up, he blamed the downtime on me. So I shoved his brown ass into every bit of furniture in the office. I took him on a tour of the office, into a few cars in the parking lot and then back into the office. People couldn't stand him so when the cops came they said they didn't see anything.
The whole "security" thing is a scam IMO. I can't stand people who won't shut up about "cyber security". These days, you have to because of regulations but it's still a scam.
If you're working with a small business that nobody knows about, you were better off not patching back then. It was just going to be more trouble than it was worth.
As a security guy, this boomer approach to patching will absolutely fuck you over. The time to patch before exploitation on recent exploits such as log4j, the exchange vulnerabilities, or that apache vuln, was under 48 hours. Anything longer than that and you were guaranteed to get hit. Which is worse, some downtime from a failed patch on one service, or every machine on the network ransomwared?
You probably have to do that today but this was 20 years ago.
The downtime was ridiculous and there was only one minor incident of hacking when the servers were not behind a firewall, using public IPs.
Services would sometimes fail to come up and there is always a chance that the server itself would crash, etc. For the email server, this was very dangerous to my job. The last thing I wanted to do is spend the weekend in the office rebuilding it from backups and backups are funny.
I've seen a number of instances where backups didn't work. If backups always worked, ransomware wouldn't be a thing.
Hacking was more of an imaginary threat like those people who say the earth is about to crash into the sun or something. I would just say, oh yeah, definitely. Meanwhile I'm adding that guy to the idiot category.
Best thing to do would be to give death penalty for these things, hunt them down like dogs.
Most denial of service is coming from these stupid MFA logins, overcomplicated permission schemes, helpdesk calls from password expiration/reset, unexpected downtime and other bullshit that is costing more than the ransomware.
Even as a developer, this is even costing me a lot of time.
"The password to circumvent MFA isn't working, someone should look into that, shit that someone is also me, now I have to call support and deal with some idiot from Sri Lanka who sends me support articles I've already read. Meanwhile, people are asking me why my work isn't done..." lol
Yeah, I get it, back then it wasn't possible to scan the entire internet for vulnerable boxes. Now its fairly easy, patching your exposed boxes, for the big easy exploits as fast as possible is critical. Otherwise the threat actors will patch them for you so they don't show up on vuln scans, and can buy themselves time to lateral.
Even pros fuck up. I know of one very capable embedded guy who supports multiple companies, who has at least one or two colossal fuckups during the course of a project. His fuckups are usually several layers deep involving complicated interactions between modules or rare stackups, that only uGod himself would have forseen.
However, the fuckups I see today in commercially released software are superficial fuckups; obvious errors that students learn about their first two weeks. For example, I've seen this particular error SO MANY F-ING TIMES:
object reference not set to an instance of an object
If you know what that error means, enough said.
Don't get me started on the stupid shit the MS Office I'm forced to use does on a regular basis...
object reference? He's doing embedded in something other than C??
No, I was giving two examples. One example in embedded land, where the fuckup is several layers deep, where even an expert would struggle to catch it. These errors get caught by skilled pros, we don't see these too often.
The other example I gave was a toilet-paper degree H1B pajeet programming in C# for example, who has absolutely no clue what the fuck he's doing. These errors are being shipped out the door on a regular basis.
(post is archived)