At a previous role, we needed nanosecond precision for a simulcast radio communications system. This was to allow for wider transmission for public safety radio systems without having to configure trunking. We could even adjust the delay in nanoseconds to move the deadzones away from inhabited areas.
We solved this by having GPS clocks at each tower as well as having the app servers NTP with each other. The latter burned me once due to some very dumb ARP stuff, but that's a story for another day.
Many are! I live in NY and 511ny.org has a great view of all traffic cams in the state (and some beyond it, but I don't understand how they got on the list...)
That's true of a lot of "Enterprise" software. Microsoft enjoys success from abusing their enterprise customers what seems like daily at this point.
For bigger firms, the reality is that it would probably cost more to switch EDR vendors than the outage itself cost them, and up to that point, CrowdStrike was the industry standard and enjoyed a really good track records and reputation.
Depending on the business, there are long term contracts and early termination fees, there's the need to run your new solution along side the old during migration, there's probably years of telemetry and incident data that you need to keep on the old platform, so even if you switch, you're still paying for CrowdStrike for the retention period. It was one (major) issue over 10+ years.
Just like with CloudFlare, the switching costs are higher than outage cost, unless there was a major outage of that scale multiple times per year.
that IS the lesson! there are a million questions i can ask myself about those incidents. What dictates they can't ever screw up? sure it was a big screw up, but understanding the tolerances for screw ups is important to understanding how fast and loose you can play it. AWS has at least a big outage a year, whats the breaking point? risk and reward etc.
I've worked places where every little thing is yak shaved, and places where no one is even sure if the servers are up during working hours. Both jobs paid well.. both jobs had enough happy customers
Exactly. Enron was a publicly traded company doing weird circular financing stuff. It was all in the open for anyone who cared to look. Just no one did until the music stopped...
We’re a bit too far if we assert this. The weird circular Enron stuff wasn’t all in the open, was by wholly owned subsidiaries, and the downfall was massive trading losses that could no longer be hidden by shuttling money to and from subsidiaries at the right time. A hole in a balance sheet is quite different from a purchase done by financing, thus “circular financing” when applied to both means “things we worry about that involve payments between 2 entities”
Unfortunately that link to the Zen of Palm PDF is broken (at least from my work machine). I couldn't find it in the Internet Archive either. Any suggestions?
Asserting that it's impossible or meaningless to measure the quality of a UI is to deny the entire field of UX research. Yes, it's subjective, but you can meaningfully measure the average across many humans. And that's exactly what you should do if you're trying to decide on a UX that will be used by many humans.
Rather than it being meaningless to measure the quality of a UI, I meant that even a UI that tests well generally might not be the best UI for a particular person.
Sure, but if you measure that for a ten thousand people (controversially, ten thousand people that aren't already programmers may be better) you can get a good idea of what is efficient and what isn't.
Maybe, but also maybe not. Ten thousand people giving ten thousand uncorrelated responses is also a possible, not unlikely result of such a test. There's also the question of whether or not your methodology for "measuring" what is effective and what isn't is even possible, let alone sufficient for a definitive conclusion.
I use Bitwarden on Android and on web and it is aware of app IDs and (usually) correctly maps them. If it's missing, you can force the mapping [yes this is moderately dangerous] and report it to Bitwarden so other users get the benefit.
We solved this by having GPS clocks at each tower as well as having the app servers NTP with each other. The latter burned me once due to some very dumb ARP stuff, but that's a story for another day.
reply