they HAD a parcel-only service. They separated it. Hello PUROLATOR, the least effective courier service on the planet. They can’t find my 31-story building while they’re standing 100ft from it. Like, LOOK UP, IDIOT. And so I have to go to the airport almost, to get my package, if they haven’t just thrown it into the ditch and cursed at it in French or something. “Alors, avez ca trou-d’eau la-bas, putain!” or so.
Oh my god.
sh -c "$(curl -fsSL https://raw.githubusercontent.com/knadh/listmonk/master/
We absolutely need to stop this. Sure, I saw the disclaimer, but we need to end the normalization of running ANY black-box crap off the net. “curl|sh” needs to be laughed into exile for all our safety.
The easiest thing needs to be the right thing – common security saying
Then it’s
vim
As if that’s actually user-friendly or a positive experience instead of the worst thing to ever survive from the last century, crawling along on its rotting flesh and drooling on the pavement like some toxic residue from the vietnam war that it is.
In what asylum do you have the people willing to suffer vi and who also need a curl|sh
? Are they lazy or just misled as noobs into thinking vi is the only editor out the–
You guys, I just realized how vi masochists actually reproduce. It’s like zombies, guys, eating brains until the victim raises up another zombie.
And that curl|sh
– does it invite supply-chain exploits? Ohhh, you bet it does! Best black-box script ever! Use this as a test for your security people – if they gauge this as a threat from within another threat, they pass. But, honestly, had it not been for the horrible spelling, I wouldn’t have thought to check further. \shrug. Mineshafts and canaries I guess.
some aspects of programming have really been made obsolete
I’d agree that some specifics have been made obsolete. Some habits and routines are currently being ignored or skipped, but the amount of skill that’s gone away is very small.
As mentioned before, we downsized brutally after Y2K. The people most affected were the highest-paid who weren’t the best code-grinders, and these were the documenters, the programme people, and the mentor types. We lost our guides, our structure, and our historians. We’ve been growing again like feral children rebuilding society from the wasteland like it’s Mad Max, and there’s a LOT of the Why that we either don’t know, that we ignore, or that we skip in the interests of (insert manufactured urgency here).
We are re-learning some of the whys, but we haven’t yet seen the half-assedry chickens come home to roost on that. The symptoms are there: Boeing’s Gilligan’s Island in Space, supply-chain sploits in waves, personal information lost weekly, all these things that are clipboard hassles we stopped doing that pelrevent massively expensive things later.
Crowdstrike may die now, mainly because they were marauding leopards we allowed to eat our face. Solarwinds before that, same issue but they seem to be okay. There are dozens of ohShit moments that could lead to similarly preventable problems, that we knew not to do … once.
Well get there again but we’ll be rediscovering a lot of what some techbro will claim is obsolete, old-practice, too-cautious, hand-wringing in our neu and moderne go-hard/break-lives paradigm.
It was a fancy lie about their spare time, but especially in dotcom, there IS no spare time to learn architecture.
What I’ve seen of dev AND ops is that their knowledge is focused well on their own things. And when it comes to the other half of devops they just want the shortest path back to doing their thing. This has caused absolute princess devs to be nearly screaming about the hassle of security and change control and infrastructure and proper code deployment and testing and … Well, a lot of things.
It doesn’t pay to have people learning to half-ass dev because ops is your thing. You need advocacy on both sides of that line, still.
What she knows and they don’t is that there is never competition between commercial providers of healthcare. America’s been trying that experiment for years.
What it gets - since there is never enough healthcare - is massive disparity in public and private services (if any public ones are left) based on your HMO’s ability to pay.
This is a challenge to our charter.
Staff quit during or after COVID.
As to why that happens, I’m thinking you can only see so many people
before you decide to switch to goat-farming and stop being a doctor or nurse.
(Like an EMT at 0830, I guess)
just because politicians are incapable of doing their jobs properly.
We work differently here. Put the brush and the America paint away.
(As a former service member and someone whose name is forever on their conscription list, should it be needed, and whose oath to the Queen has been taken up by king and steed, I have a vested interest in the kinds of conflicts we send our troopies to. Sorry if it looks different as you rail in homeroom)
Biggest pain point was for our ops guy, who constantly had to stay behind to perform upgrades and maintenance,
This is weird.
Hosts selected for updates will be unavailable from 2100-2110 or so. Then they’re up.
They’re done by at/cron if they’re selected.
There’s no manual work if the monitoring system thinks they’re okay.
Gitlab-ce on-prem. Although that may now suck since they’re being bought out; and we all know how that went for redhat.
I worked alongside some technical writers in the early post-y2k years at SCO. This was before they sued IBM for code misuse and died by a million legal and PR cuts, thanks to the ‘independent news’ site launched by a ‘recent ex-employee’ to reframe things then and rewrite history after.
We had about 15 tech writers in the company, which when I first arrived seemed like a LOT. I’d never met one, and I’d taken a single tech writing course in college as a filler and found it unchallenging work; so I didn’t value them at the time aside from filling a necessary role that your average nerd could surely fill. Then I saw their work; and it was amazing. It’s one of the product’s strong points, and 20 years later it’s still so head-and-shoulders above the similar offerings by others and since, that it’s a joy to read when I come across it.
Quite simply put, technical writers explain something in a logical, sensible way, where jargon doesn’t blind-side the reader and layout and language are consistent and easy. Hell, spelling is correct; which is a big win over 90% of the current stuff. Tech writers are writers as Lance L said, and thus know about adjective order, prepositional placement, the difference between ‘backup’ and ‘back up’ and all its similar terms; and of course know why e-mail and traffic do not get an S as nouns - ever - even if the popular kids make everyone say it without thinking.
It’s all simple-sounding stuff, and I was fooled into believing it was mundane; but when put together and written with an eye toward a common style it takes a stressful reader looking for a process or a parameter and induces calm for that brief moment required to get into the doc and find the sought-after bit.
Honestly, like the mentors we lost as a working society in the post-y2k bust when the c-suite cleared the ranks of things they didn’t understand, the loss of good technical documentation has a generational effect and will take a massive, sustained effort to reverse.
Docker always feels a little corporate.
I work in an ‘essential service’ environment for my main gig, where lots of checks and cross-checks need to exist. And it’s one that’s been under constant low-grade attack forever as it contains a LOT of tasty PII (personal info) and therefore has regs hammering it into shape. Docker cannot play here - and neither can Debian, actually, nor its derivatives - because it lacks the signed validation available in peer products sharing its space. As soon as the adults show up and notice a product with reduced validation is in place where a better one exists, the people owning that system have to write a life-cycle plan to upgrade, and it’s reviewed at an almost punitive frequency.
So, if you’re saying it’s a little too Corporate, I’m thinking you mean ‘suits and power lunches’ and not ‘large scale management of crucial systems and essential data’. True?
Does the article say how the Alexa unit has absolutely no access control? Kids ordering dollhouses? Check. The news on TV triggering a response? Daily.
They can’t expect us to link our visa cards to something that doesn’t even know “this is little Billy” – actually it can discern people – “who should never be able to buy stuff” – which it can’t do.
The units are bad: no authorization and no auditing. Neighbor tried to order you 200 rakes as he rolled past your garage? You’ll get your f’n rake back, Dennis, just fuck off and don’t bug me every month.
How has Polievre not tried to capitalize on this tragedy to pitch his “your bank is a better death panel than the transplant math” plan yet? American healthcare is half his platform!