I always have to look this up. This is my attempt at remembering, as well as offering a single, easy to find location for these techniques.

Depending on how you phrase your search, you will likely end up at one of the following stackoverflow questions, each of which is worthwhile. The information presented here is drawn from those questions, a couple of random macrumors.com forum posts, and the NSString, NSMutableString, and NSArray class reference pages from apple.

…

I hacked up my cube last October. I was becoming more and more discontent with sitting in front of the computer all day, and all night, and most of the weekend, etc. After around six months I thought I would reflect on the decision. This is how it turned out:

The lower standing area - on the left

The lower standing is positioned to allow comfortable reading/writing/typing and shows the MBP featuring The Great Wave of Kanagawa (Hokusai); also notice the whiteboard - more on that later.

…

Be sure to check out the poll, the poll’s HN comments, the raw results, the initial analysis, and the initial analysis’s HN Comments. Big thanks to Utkarsh for putting this together, making the results public, and expressing interest in the opinions of others regarding the data.

These were some of the metrics I wanted to see. You’ll notice that all of these are proportional comparisons; y is always out of 100%. This is because there was no consistency in the number of submissions per category, per user. It might be interesting to repeat something like this, but limit each user to one-one-one submissions, and then allow multiple submissions. Then we could really say things like, ‘Ruby devs like VIM’ and ‘objective-c users like xcode’. As it stands, I can say things like, ‘around 75% of activepython users did not indicate any alternative IDE usage’ and ‘fewer than 5% of devs using textpad indicate that they develop in ruby’. Not quite as meaningful, but the comparison tables are interesting (although predictable); and came with a couple of surprises.

…

Getting started in open source is an interesting road. If you search the web for “getting started in open source”, you find a slew of posts that detail basic steps like:

1. How to pick a project.
2. Start by listening in (irc, mailing lists, forums, bug trackers)
3. Commence participation in small increments. Answer questions in forums, make small documentation updates. Generally familiarize yourself more with processes.
4. Move slowly and confidently into larger updates and closer to core contribution over time.
5. Congratulations, you made it.

These are accurate details, and I must admit that I was guilty of this same series of steps in an earlier post. However, I think this is like saying:

…

This is another reason I enjoy Open Source.

Earlier today WordPress announced its 3.1 release with codename “Django” (The page has since changed). Checkout Hacker News to see more specific details about how this unfolded.

The basics go like this:

1. Matt M. posts a release announcement in the WordPress.org news. The post details that the 3.1 release is codenamed “Django” after Jazz musician Django Reinhardt. It is worth noting that WordPress always names their releases after Jazz Musicians, even if you were not aware of the practice.2. The announcement hits Hacker News (and probably other locations), and Python users start their WTF campaign. Trademarks, copyrights, respect, good practice, etc.
2. Notably, Jacob K (from Django) posts a reasonable and tempered request for a change to the codename.
3. Within about an hour, Matt M. updates the post; and now you will find that WordPress 3.1 will be codenamed “Reinhardt”, in honor of Django Rienhardt.

A couple of posts highlight possible legal issues of the codename, and there are a few fan-boy/troll posts shifting one way or the other. But in the end, a couple of high-level representatives for Django and WordPress had a documented interaction, and the result was WordPress deciding it would be better to use “Reinhardt” as the 3.1 codename.

…