[Sent from my iPhone 4S]
[Sent from my iPhone 4S]
Regarding the “de-anonymizing” the web, two years ago in Paris, I met a mathematician working on pattern detection models. He focused on locating individuals simply through their cell phones habits. Even if the person buys a cell phone with a fake ID and uses it with great care, based on past behavior, his/her real ID will be recovered in a matter of weeks. (As for Facebook, it recently launched a snitching program aimed at getting rid of pseudonyms — cool.)
Click through to mondaynote.com and read the entire post. Very interesting thought piece and probably not far off the mark.
Apple and Nokia settled an IP “misunderstanding” that also resulted in a “Tax”…but it was Nokia that played the T-Man role: Apple paid Nokia more than $600M plus an estimated $11.50 per iPhone sold. Where were the handwringers who now accuse Apple of abusing the patent system when the Nokia settlement took place? Where was the outrage against the “evil”, if hapless, Finnish company? (Amusingly, observers speculate that Nokia has made more money from these IP arrangements than from selling its own Lumia smartphones.)
This pattern is common to all great programmers I know: they're not experts in something as much as experts in becoming experts in something.
The best programming advice I ever got was to spend my entire career becoming educable. And I suggest you do the same.
learning how to learn is more important than learning anything else. If you know how to learn, you'll reduce inertia and emotional investment in any particular niche, so you're likely to make better decisions when choosing what to best work on. Another consequence is that it's best to be continuously introspective with regard to what you're doing versus what you should be doing. Often that gives you unexpected insights. If you're a good calligrapher and grok the emergence of the printing press, the smart move is to be the first font designer.
Ten minutes later, new question. Same process:
- Gather everybody around.
- Answer the question, and explain the philosophy.
- Make sure everyone understands the thought process.
- Ask one person to write it in the manual.
- Let them know they can decide this without me next time.
After two months of this, there were no more questions.
Sounds simple, but sometimes getting people to think for themselves requires you to repeatedly explain the thought process...