I like how in all of these modern APIs, they’re finally realizing that the first thing a developer looks for is an example.  It’s often right there on the front page.  They don’t want to read through a page of crufty descriptions of all possible uses when an example explains it clearly.

Open Source ain't all cake and pony rides

For a corporate web application, I was looking into using an open source DLL that was under the Affero General Public License.  Initially, I thought it’d be free because it was open source.  In this case, it turned out it’s only free for commercial use if you publish your own source code.  Otherwise, you have to pay for a commercial license.  This might be ok in the right situation, but I learned from this not to just assume that open source libraries are free in all cases.  Check those licenses carefully before you do anything!

Let's get on those story points 'cause I'm worried about the velocity of the burn down.

In scrum software development, there are all these ridiculous special phrases like “story points”, “burn down”, etc.  Specialized phrases always annoyed me.  Why can’t you just speak in plain English?  Why do they have to invent these silly terms?  Is it just to protect the trademark of the process inventor?  It’s kind of like Bananagrams…great (and stressful) word game, but instead of “next” you say “peel” and “bananas” instead of “done”.