This self-fellating cultural revisionist drivel is exactly the sort of meta-analysis I'd expect from someone who has spent too long codependent with academia and thusly suffers from an irrational self-hatred and tunnel vision and a lingering feeling that their qualifications are much narrower than they'd like to believe. The author only once cites an external party (three links to the very same blog along with a link to their colleague's book). Even that study says:
> The proximate cause of inefficiency in at least some cases was the workers' refusal to accept more machinery, but the choices of workers correlated with the local real wage. Whatever constrained the choices of workers in cotton textiles, or whatever determined their preferences, must have applied to all of the local labor force. Unfortunately the sources on the textile industry do not allow me to go with any confidence beyond this limited ascription of responsibility to local influences.
So workers in Bombay, who were being payed less than workers in England, refused to take on more responsibilities until they received higher wages. Sounds pretty fair to me. Given the information at hand, we could posit that Western countries were more successful at organizing labor instead of assuming, like the author does, that it can be fundamentally attributed to culture, and that less-developed countries like India should just adopt Western culture. Maybe if they adopted Western culture, they could come colonize Western nations, then they'd be really successful. /s
I can't see this as anything more than some sort of strange philosophical flexing, and the author could stand to get another degree--perhaps this time in history.
Adopters of the 'new' PayPal interface can probably attest to the poor quality, redirects and unexplained errors that have been popping up. After talking on the phone with two service reps, one of whom refused to let me talk to a technical expert as to why my email confirmation token wouldn't work and another who had to enable automated billing on my account manually (because it's totally broken in the client interface) I can only conclude the problems are widespread and currently still at large. I'm not surprised they have made a high-profile canning.
I transitioned back to the old interface almost immediately. The search interface for past orders is less powerful because you now need to know when an order was placed in addition to having the transaction ID. The old interface can pull up an order without having the approximate order date as long as you can provide either your own txnid or the customer's txnid. Additionally, I was no longer able to pull up orders using the customer's txnid. So, that was a bummer.
Same here. They probably have an index on the txn ID, search is pretty quick that way, but on the new interface where they force you to search within a time span, it takes forever when its more than a few days. So the decision to force people to pick a time span is probably hurting their DB select as much as it is hurting the user experience.
Yeah, PayPal works nice for the simple case, but it seems like any minimally complex payment structure, even simple recurrences, are a complete train wreck.
"The biggest determinant of shrinkage is whether the shirt went in the dryer or not. (We wash and dry all t-shirts using a warm wash and normal/warm dry cycle)."
That doesn't answer the question, which is an interesting one. Where in the dry cycle does shrinkage occur? If you dry on hot to slightly damp, do you get the same level of shrinkage as cool to fully dry? If so, why haven't I ever seen a dryer that starts hot and transitions to cool as the clothes dry out?
If so, why haven't I ever seen a dryer that starts hot and transitions to cool as the clothes dry out?
I'm pretty sure that all of the three dryers we've had in the last twenty years had a permanent press setting that does exactly that. Our current one certainly does, and it's just the front-loader that was on sale at Home Depot, nothing fancy.
But they call it "permanent press" so those of us who didn't study domestic science don't know what it does ;)
Yeah, fair enough. Come to think of it, I don't even know why I know this. Our current dryer has something on the display that says something to that affect, but our previous ones were old school analog dials without explanatory text, yet I always knew that "permanent press" meant it starts out hot and ends cool so the clothes don't wrinkle.
jQuery is usually cached in your browser because of how common it is. From what I understand, the slowing is negligible. Part of a developer's role is to mitigate site performance with the speed of process. Inlining of critical CSS is one way to balance out initial page load, for example.
This is part myth. The chances your site has the same version of jQuery that the visitor's browser cache is are pretty low. iirc, someone once said it was less than 5%.
