520 karma · joined March 21, 2008
[ my public key: https://keybase.io/justindz; my proof: https://keybase.io/justindz/sigs/3imY_SxyZxtiWMuT0BWl0I5oY2hB5_EnDR_Qhplm0UA ]
EDIT: although I must admit that she nails it sometimes - turns out the under-desk cycle and the rotating push-up handles are portable, useful and multi-tasking friendly.
Also, people who are living longer as a result of advances in life-saving surgery are doing so in poor health as a result of the reasons for the increased necessity of these surgeries such as coronary heart disease and type 2 diabetes. Increasing the retirement age in this context could mean attempting to employ a bunch of people not fit to be productive, in a worst case scenario.
With Twitter, I don't have to waste my time ignoring the latest Knighthood Invitation or the Group Created to Get Enough People in the Group to Advance Cause X w/ No Substantive Effort Invitation.
But, since our job is also not to support the LCD but the GCD, I would still support this. I would have taken more Japanese, or possibly another language, if I didn't have to take Geology. I likely would have also substituted more Philosophy for Communications. That would have been a better supplement to my CS coursework and wouldn't have made me a less well-rounded person.
I'm not saying labor cost isn't a disadvantage. I'm saying you're treating it like the necessary and sufficient condition for success across the board, which it really shouldn't be. You're suggesting that if you have a labor cost disadvantage, it is intellectually obvious that it's impossible to stay ahead of your competition with advances in other areas (like RnD or supply chain efficiency)?
I'm not disagreeing with your main point. But I think you're either selling innovation a bit short or you're being too rhetorical.
But out-of-the-box thinking is a good thing to be doing whenever one can.
At least it's not Math.sin!(), which seems more unrepentant.
There were also some instances of things like a parent having a child node and the child having a name sub-node instead of a name attribute on the child, where the parent had a name attribute. I realize there are no inviolable rules about when to use an attribute versus a tag, but what I ran into was inconsistency within a single response object. My point above was that the envelope is a standard, but the contents can be poorly designed and is domain-specific--the same is also true for REST.
I've been the client to a few SOAP services which were "standard" but which contained object representations implemented by people who probably learned XML while severely inebriated and chose their tags vs. attributes using some Post-Its and a dart board.
This article did bring up a question I had with Firefox on apt-based systems. Why would I install a Firefox plugin through apt rather than just through Firefox plugins? Is the argument basically the same--that there are fewer/older plugins in apt but they have been proven stable by someone you can decide to trust so you get to choose what you care about most?
And, no, I don't think Cameroon is financed by the World Bank. I just wrote that poorly. I was interested in understanding whether the natural incentive to build an economy to increase the scale of possible graft (not my theory, from the article) could be killed by getting outside funding that, perversely, wouldn't result in a more successful economy if it were being hoarded. Perhaps that just doesn't happen.
Is that about right?