Finally, DevOps has caught up to the rate of progress in js framework land. Rejoice!
13,805 karma · joined February 5, 2014
Email username.co at gmail
"I'm moving overseas for an extended period of time." (Implication: to somewhere you don't offer service)
"Where are you moving?"
"I can't really say."
Turns out, most service providers have an exclusion to their retention metrics, where "customer moving to location we don't offer service" is one of the few reasons to just process their cancellation request.
White collar architects are artists, and spend their time designing. Then they hand their sketches to structural engineers and say "Figure out how to build this." These are generally the folks architecture magazines write about.
Blue collar architects are more engineers and tradespeople, and see success as a building that fits the purposes of the client, in budget, in a pleasing way. They're more likely to repurpose a historical form, if it's well suited for the request at hand.
One of the central features of architecture meta is that white collars think blue collars lack creativity and intelligence, and blue collars think white collars are pompous pricks.
Among other problems: (1) no provision was made for the fact that Cleveland gets snow and ice, leading to barriers for pedestrians to avoid their evisceration via detaching ice sheets from the curved roof, (2) the glare off the roof is focused straight down a nearby street @ 5pm, creating driving hazards, (3) it's difficult to navigate internally from one side of the building to the other.
Most star architects are hacks, coasting one step ahead of being made to answer for the flaws of their previous projects. The more famous the architect, the more they feel obliged to ignore basic design.
Or, in other words, they don't have their own version of this strategy chart: https://johnaugust.com/wp-content/uploads/2014/07/disney_cha... (Disney corporate synergy, dated 1957)
Your primary consumer has the attention span of a 10-year-old, and no disposable income. Why are we surprised this is a terrible industry?
A smarter approach would be what Tim Sweeney is talking about with Fortnite (and Amazon infamously does): you have to do everything you can to pivot any initial success into a durable advantage, by aggressively expanding into adjacent opportunities, even if they're very different businesses (e.g. movie theaters).
They've made token moves towards this with the physical toy + computer game mash-up genre, but from an external perspective I don't think any of them quite get how it's supposed to work. Efforts seem under -capitalized / -resourced / -inspired.
Anyone can claim anything they want.
What is relevant here, and why this case was decided the way it was, is that the federal government and the tribe entered into a legally binding, clear contract.
Lands east of the Mississippi in exchange for a large piece of what is now Oklahoma, in perpetuity.
And Congress never explicitly reneged on that contract. Ergo, it still stands.
Should the Mohawk produce a similarly ironclad agreement regarding New York, they would then have a claim.
So are you buying Intel stock now?
What it could probably not do is run-on-ARM with acceptable performance for every legacy app.
Windows' bread and butter has always been forever-compatibility (Win API language-of-the-year aside) for long lived business apps.
Apple has never, and doesn't seem to want to, competed on that front.
And for the same reason that we don't allow health insurance to charge people different rates on the basis of their genetic profiles, the exercise of government prerogative to optimize for the greater good, on behalf of all, is apt here.
Whether or not this particular approach is the best way to produce that good is a valid debate.
My point being that they still deploy a lot of low-level data science against data sets to prepare a view for human interaction.
And their typical customers have limited ability to do that prep in-house.
Also, younger folks these days haven't lived through a physical media migration.
The weirdest thing I remember about the early CD-ROM days was that everything was parallel distributed: there was a floppy version (10 disks!) that would be substantially media-cut-down, then a CD-ROM version. Because install bases don't grow overnight.
Experienced teams who have designed high performance microarchitectures aren't common, because there just isn't that much of that work done.
And when you're eventually going to spend $$$$ on the entire process, even a 1% optimization on the front end (or more importantly, a reduction of failure risk from experience!) is invaluable.
E.g. a tradesperson will generally be out day-of in a metro, vs that very much not being my experience in the NE.
Neither of which they executed on.
Btw (because I also peeked at other links), if another UX discovery data point re: pharma research would help, flip me an email (in profile). My father just retired from T10 drug discovery R&D (pathology), and would probably be willing to talk your ear off re: process issues.
Budget caps seems like a cop-out though, as eventually the budgetary rules inherit all the complexity in the current technical rules.
I think some kind of FRAND forced tech licensing / transfer + shared manufacturing would be an interesting solution. Whereby a hyper-optimized solution by a leading team can be licenses (or is outright open sourced) for the next season. And similarly, where all builders have access to a neutral manufacturing facility (a la TSMC).
"Kimi!!! How did you feel the car was today?!"
"Car was good." walks off
Economists have always befuddled politicians.
Unfortunately, the collision of the two typically leads to the worst of all outcomes without the benefit of any. E.g. Implementing protectionist policies without a low term plan for their withdrawal.
(It's not something I've spent a lot of time looking at)
That's exactly what's driven me batty about governments' responses.
After the initial lockdown, that's precisely what they should have done.
Instead, we got a schizophrenic "Everything is fine" and then "Everything is danger! Surprise second lockdown!"
No wonder people are pissed. It'd be better and more effective policy to just lay out the methods, criteria, and current status.
(PS: Technically, you're talking about R_t, or current, rather than R_0, or initial)
What will passengers think about having their ride delayed? Lump it into Pool and partially rebate them?
What will keep restaurants from #&@$ing around with their notifications (e.g. ready) for a partner who they don't really like working with?
(Personally, I switched to Lyft and don't use Uber products anymore)