Hmm, I'm still using my Note. I don't have any facts, but I'm pretty sure it still has a nontrivial user base. The hardware is certainly powerful enough to keep up with anything I demand of it.

I think the issue with the Gear is that Samsung noticed people with larger phones springing for Pebbles and such, and rushed late to market with a product that wasn't ready yet. The original Note identified a niche that was largely unexploited prior to its release.

This is correct. Headlines are often written in the passive voice, e.g. 'Iraq Bombed' rather than 'So and so bombed Iraq'.

I can't believe how many hours of my life have been spent jumping around Ironforge aimlessly.

Work remotely. Block off time in which to be productive on your calendar. Turn your phone off. Log out of any instant messengers.

If you can't work remotely, find a conference room.

read the search query

Wow. Today is Erlang day at HN.

I think the point was to be pretentious to the point of irony, which the namedropping achieved.

Yes. My point was only that not knowing the names so dropped doesn’t actually diminish the story, because they didn’t really have any deeper significance.

All of them married to the same man?

Obviously I mean 'they are all married to women', but your interpretation is much more amusing.

Too much sex with women leads to marriage with men?? LOL

You know, I had a Sony mp3 player a while back. One day the music library software updated itself and installed DRM retroactively on the device and I could never change the music that was on it; I threw it out after I got tired of hearing the same 12 songs.

Yes, 12. 64mb storage =]

I'm almost positive that around the time of 64MB storage, Sony was still very against MP3 and refused to support anything but ATRAC3.

Although English doesn't emphasize gender in nouns, in romantic languages (which are the basis for English), that class of nouns is masculine.

Where the gender is not known, the correct pronoun is "he." A spokesman is a he; a spokeswoman is a she; a spokesperson is a he.

I don't even bother with that struggle you described anymore.

Get assigned ticket for new feature. Write test outlining how it would work with the assumption that the existing code does what it says it does.

If you find - surprise! - the code doesn't do what it says it does, create a ticket and recurse.

Compared with trying to make the tiniest possible change and running into gotcha after gotcha, this is a far more sane and sanitary procedure. It takes longer, but in the end "your" code meets requirements and you can prove it.