That’s not just annoying — that’s infuriating. But I don’t have a category for that and don’t feel like adding one.
A good example of when things were definitively superior in the past, and are now horrible and anti-user. No matter what any clown claims.
Domain Controller is a Dell running MS SBS 2003 R2.
Domain controller is a what now?
That requires archaeology, not a migration. Start fresh. It’s so much better than trying to migrate that crap. Yes, it can be done and I in fact have done it in the past (long ago).
But why bother?
I had a 56k modem but it never connected at that speed. I got 48k sometimes. Most often 33.6.
I started out with a 1200 baud back in 1985 or so. Then 2400, 9600, 14.4, etc. Now I have 1Gbs symmetrical fiber and it is infinitely better.
First year IT Support and I’m treated like a dog
This is common in IT. It’s probably even worse if you’re a woman (as this poster is).
Most people see anyone in IT — no matter their title or role — as the computer janitor/servant who should be completely subservient and willing to do whatever bullshit no matter how unrelated to the job or what the business needs. I’ve seen it over and over again. And I’ve lived it.
There’s some good advice in that thread (as well as some bad). Her boss should be doing a much better job of having her back. If someone treated one of my people like that, I’d be raising hell and blowing up the CEO’s inbox and Slack. That’s what’s a quality boss does.
And it never ends! I make well more than $100 an hour and I still spend time helping people unmute their headset. Or plug in a USB thumbdrive correctly.
Makes no damn sense.
Why firms are merging HR and IT departments.
My god this is a terrible idea. I can’t imagine how horrific this will be for the company, for IT and for the end users. HR is more clueless about IT than anyone can even imagine.
There is no chance at all this well go well anywhere long term. None.
What’s an IT “truth” which other departments assume, that really annoys you?
That anything that uses electricity, or that has any moving parts, is IT’s responsibility to provision, troubleshoot, replace and maintain.
I know it’s because we have the only population with methodical and reliable troubleshooting skills but Karen, nope, I’m not gonna fix the coffee maker. And I’m not gonna unjam your stapler and definitely will not help you do your own team’s job, either.
Or any assorted crap you find on the internet. AI is no different than any other tool. You don’t just copy and paste code snippets or scripts of unknown function or provenance and hope for the best, no matter where they come from.
My question is after this screw-up, why did it take six entire weeks to diagnose and fix? This is something I (or honestly, anyone competent) could’ve figured out in a part of an afternoon once the junior put the bad PowerShell in the SCCM baseline.
Not a hard problem. Not with all the evidence already available and easily gathered. Most people are incredibly poor troubleshooters.
Fucking Windows 11.
Just did a shutdown /s /t 0 /f at the terminal and guess what? Restarted instead.
Fuck you, Satya. Fuck you very much.
That is pretty stupid and clueless.
I understand IPv6 just fine and have set it up from scratch many times in large networks.
So I can very confidently say that it really sucks. It was designed in the 1990s before we understood any of the problems we’d be facing in the 2020s. And it shows. It’s creaky and ill-suited to its actual use. It has security assumptions that aged poorly (IPSec everywhere? Sure, Jan.) and features that will never be used. It’s mostly cruft and useless crap with some ok functionality if you’re using dial-up.
First, its human-unfriendly addressing makes diagnostics, documentation, and training way harder. No fucking one alive can remember or understand just by looking at it what 2001:0db8:85a3::8a2e:0370:7334 means or does. (For my non-techies, that is an IPv6 address, like 192.168.1.1 in IPv4).
Additionally, no matter what you’ve read, NAT actually is a great security feature and IPv6 only begrudgingly supporting this is clownish and harmful1.
The crack I made about dial-up earlier was actually leading to something. IPv6 was designed long before cloud-native networking became a thing. That means it was created when it was implicitly assumed that all hosts had one interface and one static address. These days, containers, VMs and ephemeral workloads are dominant. IPs change all the time, get re-assigned and altered, sometimes every few seconds. IPv6’s assumption of a static architecture makes it poorly-suited to dynamic cloud environments.
Also, for we admins, things like stateless address auto-configuration (SLAAC) and router advertisements give us less control. We actually need this control and visibility for security and observability. Allowing IPv6 to do its black-box magic is not any advantage for us. It is in fact actively harmful and makes networks much harder to secure and administer.
IPv6 also assumes end-to-end connectivity is a good thing — that everything should have a public IP address and be on the public internet 24/7 (related to my point about NAT above). Bro, I don’t want my washing machine or toaster on the internet. Trust.
Subnetting in IPv6 is also absolute crap. “Just use a /64 everywhere!” Why, god, why? This just adds complexity, not reduces it. Insanely dipshitty.
And don’t get me started on the fucking idiotic link-local address. For those not in the know, in IPv6 every interface gets assigned a link-local address to talk to its neighbors. This is bad! It’s not routable, is a security hole, it causes problems in logging and diagnostics and with multi-hop while being confusing and inobvious to most network admins.
Of course, IPv6 also replaced ARP with NDP. This inefficient-as-all-hell turd of a protocol has more useless steps, a larger (and difficult-to-audit) attack surface, is far, far more fragile and requires complex (and also fragile) firewalling. The clowns replaced a dumb but reliable protocol (ARP) with an insecure, “smart” but fragile one. Great job.
It also has crap DNS integration. The designers back in the 1990s assumed we’d use an IP address for everything. Hostnames and DNS were an afterthought. Meanwhile, DNS is used for absolutely everything these days.
IPv6 also makes network planning far harder. Global prefix delegation, renumbering, and prefix lifetimes are a goddamn nightmare. Get it right the first time or you are screwed (ask me how I know).
And, related to a point above, IPv6 was designed for well-structured pre-built networks with planned addressing, stable routers, and consistent ownership. That means it really does not work well with mesh networks, ad-hoc clusters, cloud VMs that spin up/down in seconds, serverless functions…I could go on.
IPv6 is like giving a skateboard to a donkey. Sure, theoretically it might be able to get wherever it’s going faster. But what the hell is a donkey going to do with a skateboard in reality?
(Source: I am an active CCNP, have worked in tech for 20+ years, and have designed hundreds of IPv4 and IPv6 networks from the ground up and then built them out myself, often purchasing all the required hardware as well.)
Why did every phone brand suddenly decide we don’t need SD cards anymore?
Trying to force you to bullshit cloud data-thievin’ garbage.
The future sucks.
Agreed. Most of us are stochastic parrots most of the time. Rarely — maybe 10-15 minutes a day — we rise above that. Normies less and the extremely intelligent maybe double or triple that time.
DNS Security is Important But DNSSEC May Be a Failed Experiment.
DNSSEC is fucking moronic, harmful clownery of the worst kind. It’s a giveaway to those who want to hijack your traffic and a boon to malware.
Fuck DNSSEC. Fuck anyone who implements it.
How many of you don’t actually interact with end-users?
In my field if you’re good enough, I don’t think you ever stop dealing with end users.
Once they figure out that you can solve their problem in 5-10 minutes that the helpdesk might take a day, a week, or months to puzzle out, it is fully over. Even if it’s not the best use of your time and the company has other priorities. And often enough the “tier 1 emergency” is that they forgot how to unmute their headset.
The end users seem to be able to sniff out your problem-solving ability like some weird sightless creature from a cave in Guatemala. I don’t know how they do it, but they always find out and always ignore all protocols, escalation paths, good sense and etiquette to locate you and take you off a $10 million high-value high-impact project so you can spend time and company money researching why they cannot click a button in Microsoft Word.
A good use of time, certainly.
When the purchase price and annual support cost for humanoid robots becomes lower than the cost of training, operating, and sustaining human soldiers, traditional infantry will be obsolete. We seem to be heading towards Isaac Asimov's vision of the future at breakneck speed. https://t.co/t2W47fduQP
— Nicholas Drummond (@nicholadrummond) July 13, 2025
That’s CGI of course, but given the current rate of progress and assuming it continues, I’d say we’re 12-15 years away from that result.
Windows 11 Has a New Way To Fix Itself.
Removing itself and initiating a Linux install? That’s the only way to fix that putrid OS.