I hope Equifax will be learning from this, but can you tell your CEO that your core business must be shut down for 3 weeks as you upgrade and rebuild the system?
Yes, the risk is much higher than the cost. From the article:
> The company's internal review of the incident continued. Upon discovering a vulnerability in the Apache Struts web application framework as the initial attack vector, Equifax patched the affected web application before bringing it back online.
That bullet point lies between the "July 30th" and "August 2nd" bullet points. Based on that timeline, the vulnerability took days to patch.
I agree, there are many competitors to React for targeting the DOM, but there is much less competition for targeting Native. I hope to see more JSX-to-Native engines pop up soon to solve that problem.
This is correct. I once had a series of customer service reps deny me access to my account to the point where they told me my account was irretrievable. Irretrievable? I called back the next day and the new rep told me those other people were totally incorrect, and he resolved my issue in 15 minutes.
With high turnover rate and minimal training, most service reps are reading from a script and attempting to appease you into hanging up the phone anyway.
Some places get "rated" by the length of the calls, not number of happy customers, or resolution to call ratio... just length of calls. Keeping it short, even if it pisses off the customer is better for keeping their job.
I think a lot of people would discount this anecdote as absurd to be true, but I have found this too. I have a friend who did tech support for google and she was quantified on all sorts of naive tracking metrics that were company-focused instead of customer-focused (# of upsells, customers handled per day).
So obviously you can save money by shortening call durations. This has a nice side effect of reducing the number of customers (over time), which also helps reduce support costs.
A better metric might be cost per call. Outsourcing gives them cheaper per-call for the same length. Refusing service probably also shortens the call length. Refusing to do anything outside of the scripted interactions probably leads to some type of punishment for the rep.
could be a variety of factors. might be a small department, which means if you call back, thats another extended call for them, which is bad for the metric. better to get it solved the first time.
Or it could be simply a place that doesn't use the call length metric, I imagine every call center has its own set of rules. I can only speak for the ones that my friends work[ed] for. Overseas call centers may have less focus on call length since the cost of the call to the company is less.
> most electric bikes I see are ridden dangerously to pedestrians; by NYC deliverymen (doubt I've ever seen a woman on one), swiftly and silently sneaking up to run you down on sidewalks or the wrong way on one way streets.
Both of those uses of a bicycle - operation on a sidewalk and riding against traffic on a one-way street - are a violation of NYC traffic law [1]. The operator is the one causing danger, not the bicycle.
what you say is true, but what I said is also truly what I wanted to say, so to clarify:
NYC has widespread ignoring of many traffic laws, and that does not bother me. I am talking about, in the context of widespread violations, what does bother me: the electric bikes. You could accept that there is some validity in what I say without agreeing with me.
Given the choice, I would not be in favor of pedestrians and bikers being forced to follow all traffic laws. However, I would be in favor of electric bikes being forced to follow all traffic laws, especially the one that bans them! :)
I see, and I agree that the accountability of cyclists (and slightly less so for motorists) in NYC is almost zero. I also agree that electric powered bicycles should be held to a higher standard than normal bikes, particularly in that their use is entirely illegal so it should be much easier to spot and ticket them. I mostly posted these facts because most non-NYCers don't even realize that these uses of a bike are actually against the law.
EDIT: I just read your edit,
> I find electric bikes even more destabilizing and most objectionable, because they are faster and quieter, and I think because they are favored by a statistical sample that skews toward more selfish/self-interested.
This is a good summary of my thoughts about electrical bicycles as well.
I understand what you're saying but I think it goes without saying that we've started paying more attention to quality of user experience for software in the past twenty years.
If you genuinely disagree and believe the 90s were as ripe with quality tooling and documentation as 2016, well, that's a bit strange, but you're certainly entitled to your opinion.
I don't know. I really like the moments where Alan Kay appears out of nowhere, tells where your idea squanders the potential of computers, points to 60's-80's prior art that did it better anyway, and disappears in a puff of smoke.
The last thing our discipline needs is us thinking we got it all and it just needs polishing.
