1,484 karma · joined February 21, 2007
Edit: or from the app store now. sweet.
I would pass on someone with an attitude of hard-work and responsibility for someone with real programming intelligence (the whole package- product to interface to maintenance) in a heartbeat. The last thing I need is someone diligently corroding a code-base.
Edit: OK, I'm finding some cheaper rents, but I think my main analysis stands.
On another point, I would point out that in general adults are very, very attuned to having emotional responses to crying children (the younger the more powerful the response), whether we have our own children or not. That's why a baby crying on a red-eye flight can have such emotional reactions from total strangers (often negative, unfortunately). It's a wonderful human instinct that I think serves us very well in general. But those who aren't experience parents need to remember the following (_please_):
* Every baby has a different temperament and personality.
* Babies sometimes cry to get attention and not because they are actually in any way uncomfortable or scared. The different sounds are easy for the baby's parents to hear and difficult for other people to distinguish. (as mentioned, newborn infants are easier in that they always have a reason when they cry).
* They sometimes cry for a while and there's nothing you can do. Seems to always happen in public. Leg aches, colic, gas, etc.
The wikileaks summary on the first page implies that the government actually tried to carry out a contingency plan to get rid of wikileaks (and that it "appears the plan was ineffective"), which is beyond silly. Surely wikileaks of all organizations would understand that these sorts of _analysis_ documents, enumerating even the mildest threats and then pinpointing potential weaknesses and then basically trying to get permission to investigate further (probably unsuccessfully but who knows) are a dime a dozen (not implying you should ever pay for one if offered).
The word "planned" in the phrase "planned to destroy..." has a very different meaning in the context of government contingency planning than common usage suggests. In most contexts a plan to do xyz implies a course of action the organization intends to take. The US government, at least, generates layers and layers of "plans" that it never intends to act on, or knows that the probability that they'll need to be acted on are very remote. For the most part then the actual dispatch of some combination of plans are left up to non military elected officials.
As for the research, just to further clarify- they rigged a mac so that there was a second monitor above the first monitor (and above the main mac menu) that the mouse pointer could move to. When mac users sat down to use it, even knowing exactly what was going on, they consistently overshot the menu by an average of half a screen. I'd be highly surprised if resolution was even minimally relevant.
I remember when Microsoft made it so that you had to go to the corner but then pull it back several pixels, thus destroying forcing you to aim the mouse cursor. It may sound like a silly little thing, but I thought at the time that it was a good metaphor for how they could get something to _look_ similar (to, say, a mac) and yet still get it completely wrong. When I switched to linux around the same time I thought it was so refreshing that the UIs of the time (minus some skins people had made) didn't violate this example of Fitt's law, and also that if anyone were dumb enough to change that in the future, we could all just fix it.
I usually disregard comments about linux desktops copying window's mistakes, but this is just very irritating to me, mostly because it's elective- it's like you actually have to _try_ to get it wrong.
There are certainly reasons to be skeptical. In addition to age, consider for example the fact that it tends to be highly correlated with automatics vs manuals.
If it turns out that the thing critical to our being is deep within our neurons, and that the computations that take place are similar to quantum computing and rely on sub-atomic processes, and that the rest of the body (among other things) keeps its environment stable enough to "keep state," then the machine needed to copy the mind would end up destroying the original. Or, if it doesn't read atomic information at that level of detail, the "copy" will have a similar infrastructure but will instantly be divergent from the original because the "current" thoughts of the original will not have copied.
I mean, putting aside philosophy and actually getting down to the brass tacks so we can start building this machine. (:
While I agree about being faithful to expectations and see value in that, I also believe that metaphors can sometimes continue to live past the time they should be expired due to sheer laziness. There's only been one generation (ish) exposed to that physical interface for a calculator- it's not like it's a permanent beginner metaphor.
Interestingly, it may be that Heisenberg uncertainly requires that if you extract all of the information out of Riker in order to reform him, you must necessarily destroy the original Riker, saving you a bullet. (IANAP, _obviously_).
If flash only beats html5 when using hardware acceleration and html5 browsers haven't introduced hardware acceleration yet, his conclusions end up backwards, or at best completely irrelevant and speculative. shrug
Worth it for that quote alone. Thanks (:
—Mark Twain
Biggest. Dissection. Ever. (as a ratio to the size of the original joke, including the edit and at least 2 comments). You win ;)
shrug
It did make me start to think though about one reason I enjoy computer science (or the engineering side more specifically) - it tends to be much easier to get traction on good ideas than many other fields. For the most part, good ideas in computer science are self-evident, and easily adopted by practitioners. Too easily sometimes- without enough scientific method being applied. Of all scientific fields, computer science would be the _last_ one I'd accuse of engendering blindness to obviously good ideas. A cadre of older programmers dictating to the younger generation how to think about programming? Seriously, lol (: