273 karma · joined November 21, 2009
[ my public key: https://keybase.io/sama; my proof: https://keybase.io/sama/sigs/hRuBY7-RpJEuvGGsjdv9FsSLy6RvhpvP-6l0NARkMeQ ]
http://www.mypersonality.info/personality-types/population-g...
If you only read books, then don't blog.
If you ever saved time or got a tip or some code from a blog, then you owe the rest of the programmer community.
I think that's the right spirit.
With regards to the "privacy mode" of most browsers, I think that the feature is mis-named since it mostly refers to the browser's tracking of your activity, not the server's.
I would focus on selling yourself, not selling something. Your Pagerank should help you speak with more influence about subjects that you are an expert on, and then, use that expertise to get jobs, consulting, funding, grants or get published.
An example: let's say you have a time tracking web app. Your content can talk about good approaches to time management, or techniques to focus, or publish research about the average lengths of different tasks from the data that you can gather from your users.
A great example is Mint.com's blog -- http://www.mint.com/blog/
Other great HN discussions on SEO:
http://news.ycombinator.com/item?id=1073357
But I still see a lot of miopic behavior in the media. The battle is not between Apple and Google. It's more like: (Apple + Google) > (RIM + Nokia)
Regarding the book list, nah...
Comparing programming to an art form, and the process of maturing as a developer to the process of becoming a master, comes from the mindset of somebody who is trying to create something intrinsically beautiful.
And while beauty is a powerful concept, most software projects are trying to make something functional.
More over here -- http://blog.aparicio.org/2009/12/28/the-master-the-expert-th...
What came as a breakthrough for me was to actually mix screenshots and statically implemented screens in a real mobile app, then play a lot with that.
The idea in the post is to play with the design, in the device, for a while, and get design feedback much earlier than when you give the app to a developer.
1) Scoring system for stories (Digg) and comments (Slashdot)
2) Community based story submission (Kuro5hin)
3) Infinite indentation (Usenet and Forums)
It's also interesting to note what they didn't include in the design: Subjects for comments
HN's approach is not without challenges
1) Following the conversation gets tougher when there are a lot of levels. Who said what?
2) By reordering the posts according to points the user gets disoriented.
If it's targeted towards business, forget it, now is a terrible time to launch. For the same reason, people in business have their head elsewhere, either closing the year, dealing with the retail high season, or going on vacation.
The exception to this would be if your offering is b2b and has to do with a category that is very well allocated to an expenditure item in a budget for which there is generally speaking potential 'use it or lose it' money.
HTH