Taxi companies in most cities were exploitive oligarchies - it was textbook regulatory capture. Often their workers weren't any better off in terms of lopsided deals. And the customer experience sucked sooo bad. The smells, the illegal "cash only" bait and switch, the runarounds. I remember. I was there, Gandalf. And I'll take Uber any day over going back to the old system.
A good habit to build is knowing when to abandon a session and start over rather than trying to correct. There’s room for correction but you can kind of smell when the whole discussion has become rotten and inefficient. Sometimes it’s just better to use the session as rubber ducking to learn how to correctly articulate what you’re after and start a new session with that clean and correctly articulated foundation.
I don’t think VS Code is remotely a replacement for VS/Rider. I use VS Code for a lot of things but for large and complex project sets the automation and features in VS are luxuries you really miss. It’s like going back to the Stone Age to use VS Code in those contexts. Trying to fill the voids in VS Code with extensions makes VS Code very brittle. VS Code has its lane but I think they are different tools suited to very different jobs.
Interesting, for my part I would never build a data center (or underpin critical infrastructure) with Ubiquiti but I have a lot of it at blind remote sites and it works well enough - WAN failover, and they've built out a fair bit of downstream failover as well - shadow gateways, RPS, etc. Has replaced a lot of Meraki subscriptions.
Ooh, I'd love to hear how you've made that work because ZTD with Ubiquiti - at least in their Bluetooth app deployment era - has been a crapshoot for me.
As for data centers, I should be clear on sizing: we're talking the same sort of footprints you'd see Meraki leveraged for (<10 racks, mostly traditional storage/hypervisors/big iron stuff), not HPCs and Hyperscalers and the like. Y'know, standard VLAN-based isolation, traditional load balancers instead of network overlays, maybe the odd eBGP for public cloud connectivity with the new Ubiquiti Network update. Areas where I don't need QSFP+ to endpoints and where budget forces me to choose between hardware and headcount (an area Ubiquiti and Meraki excel in). Even then, I'd really only lean into Ubiquiti over Meraki if I'm trying to conserve capital and I'm unsure of scaling: Ubiquiti is cheaper to replace if I need to scale up than Meraki, but Meraki's support is generally far superior than Ubiquiti since it's Cisco folk.
Could I build a data center on Ubiquiti? Totally. Would I? That's highly dependent on the specific context.
"Project Gutenberg began in 1971 when Michael Hart was given an operator’s account with $100,000,000 of computer time in it by the operators of the Xerox Sigma V mainframe at the Materials Research Lab at the University of Illinois."
> a more balanced version: <bunch of weedy ACLs, judgement calls, liability/>
Too complicated and subjective, stinks of more risk.
Also, I don't think it's dehumanizing it all (having been on the receiving end of it way back when during a layoff, and involved in the process more times than I care to count). It's standard practice for involuntary terms at all companies we work with, whether employee is IT or not. If a company is not doing this already, I'd encourage them to.
> Too complicated and subjective, stinks of more risk.
I actually think there's less risk, because it's not as narrowly focused on what a just-fired employee can do. That's not the only scenario of concern.
> Also, I don't think it's dehumanizing it all (having been on the receiving end of it way back when during a layoff, and involved in the process more times than I care to count).
Interesting. Thanks for the perspective. I've been fortunate enough to not be on the receiving end of a lay-off, knock on wood. It's happened to my teammates/reports though. Wasn't my decision. :-(
corporate overlords? These are the state governments selling your data. The call is coming from inside the house. The sooner we realize that government is comprised of the same slithering slime of human greed and laziness, the more realistic discussions we can have.
It's not even remotely the same scale. At least the government ostensibly has its incentives aligned with the public. False equivance gets us further from where we need to by focusing people on the wrong problems.
"Ostensibly" is the mistake in your formula. Current events are replete with examples to the contrary. It's not equivocating to recognize that governments are organizations of humans, subject to the same limitations - the larger they get, the harder they are to manage well; talent is incredibly important to success in mission; leadership is incredibly important to integrity, ethics, and strategy; lower oversight and mediocre control structures lead to abuse. You can see the challenges that government as an organization has there. And as to scale..? Son. At least you can "ostensibly" choose whether or not to interact with corporations unless they are colluding with... government.
Consider the bulk of your comment to be directed similarly as criticism to corporations, minus effective correction mechanism, plus direct incentive to extract as much wealth as possible by providing as little value as possible.
Which isn’t to say government is bad as an institution.. just to say that we regard it with an assumption of good faith at our collective peril - it’s track record counsels the opposite.
It would be comical hear this as if you think it contrasts with companies if I didn't know you believed it. The very "slime" that leads to the government doing these things accumulates at the behest of the entities you're defending.
Honestly, we're better off with it than without it, speaking as someone with exposure to that industry's internals. That act drives a lot of good security practice within the organizations (mostly liability shifting, but still good). Specifically, the fear it instills of ruinous penalties from regulators drives good practice adoption, IME.
Further, multiple crappy patient portals across providers is a crummy experience, but it's an improvement over the world where providers held the data hostage and had zero interest in accommodating your requests for it, or even the idea that you owned it.
reply