Top of the search result page: "Did you mean: vim"
Felt like I was being trolled.
475 karma · joined October 3, 2016
Top of the search result page: "Did you mean: vim"
Felt like I was being trolled.
Also very important for me: I always have some decent clothes hanging in my closet that are washed, prepped and ready to go for various situations. Not having something nice to wear for a last-minute social event is a massive source of friction, but if I can easily throw on some clothes that I feel good about then it really dials up my enthusiasm.
(And I wouldn't characterize myself as being overly impressed... for my particular scenario I wrote, "if you have a poorly written app that's bottlenecked on a lock, then consider targeting Windows to make the best of a bad situation." A better approach, of course, would be to just improve your code!)
"We consider an adversary that is on one of the endpoints of the victim connection (i.e., it is co-located with either the NVMe-oF target or client). The attacker is an unprivileged user and is assumed to have obtained access to the machines using legitimate means. We assume that the attacker shares the same physical RNIC as the NVMe-oF entity and both can use it for communication. We assume that the attacker and the NVMe-oF entity are not separated through RNIC virtualization. The TLU model is prevalent in private clusters that use RDMA and NVMe-oF to accelerate their workloads."
An attacker is pretty deep into your infrastructure if they can even get a whiff of your storage fabric like this.
I haven't been driving as much in recent years wasn't aware of this trend. (Except for Tesla drivers: 5 years ago, I remember looking over to see a Tesla on autopilot next to me, doing 60 on Seattle's 520 bridge with the driver totally checked out and watching a video.)
I always thought CHM files were a nice self-contained option for multi-page HTML docs. (Though they'd happily execute whatever JavaScript the author embedded in there... Maybe that's why they fell out favor?)
I don't miss the battling software ecosystems (Samsung vs Google) on that old phone, though.
Thankfully there are a lot of car enthusiast forums out there that have been plugging away on vBulletin for years. Someone on an Acura forum had figured out that the bluetooth module was always on and looking for a connection. I tried disconnecting it, and the problem was fixed.
Every time I log in, a big, disorienting interstitial appears and pitches me on Experian CreditWorks Premium ($25/month), with fields asking for my credit card info. It's designed like it's part of a normal registration/login process that you're supposed to fill in. You have to scroll down past all of it to the bottom of the page and click the washed-out, kind-of-disabled-looking button that says "No, keep my current membership", at which point they reluctantly take you to your normal account overview page.
So now the chickens have come home to roost, and there's a skill shortage. You'd probably end up at Fiserv, or maybe at a big bank or some gov't agency that'll drop you at the first opportunity. You'd get a decent salary, but not a massive one.
You'd be better off working at a place that views your development effort as something that generates revenue. Rewards tend to be higher. And wherever that ends up being, they almost certainly won't be using COBOL.
The MS docs from the late '90s through about 2015 were stellar. For example, look at the Windows Sockets docs[1], which came out of that era. Here you see information architects working at the height of their power: Content is broken up into conceptual ("About Winsock"), task-based ("Using Winsock"), and reference ("Winsock Reference") topics. They were doing this kind of structured documentation before DITA was a thing. It's a pain in the ass to produce content this way, but the results are wonderful.
Then came .NET Core: a fast-moving, community-driven effort, where the philosophy seems to be to get it working and then scribble down some docs later. The result tends to be a huge wall of text with conceptual and sample topics jammed together ([2]), and you're lucky if the API reference gives you anything beyond parameter names.
Azure docs suffer from a different problem. It seems they've tried to apply some kind of rough information architecture, but the quality isn't great. I've looked at the GitHub history of some of the shoddier topics, and they're often written by junior Product Managers who are fresh out of college. I encounter a lot of imprecise, colloquial English describing out-of-date screenshots.
I don't mean to belittle the people who work on .NET Core and Azure. There's a ton of content that needs to be written for these products, and it's a thankless task for the devs & PMs who do the heavy lifting now. I'd really like to see some dedicated technical writers come in and bring the quality back up to their old standards.
[1] https://docs.microsoft.com/en-us/windows/win32/winsock/windo... [2] https://docs.microsoft.com/en-us/aspnet/core/fundamentals/ro...