FourthSegment Blog: Social Media is exploding, and it's only going to get hotter
A few weeks ago, Boston Innovation released an infographic called Social Media is NOT as Popular as You Think. The point of the article is to remind people not to get lost in the bubble of thinking everyone in the country is a Facebook & Twitter expert. This is very true. If you’re a technical…
mulligan - a Ruby idea for dealing with things that fail frequently
Note: There seems to be some weird style issues with gist on this Tumblr theme. There isn’t enough horizontal padding between keywords. Sorry.
Twitter fails a lot. It got me thinking about an elegant way to deal with things that fail frequently. This is how I wanted to be able to write code:
Here is how I accomplished it:
I’m gonna tweak it into a gem eventually, but I want some nerd feedback first. I can see a whole bunch of options being added: which exceptions to catch, custom handlers, etc…
What do you think?
OSI layer 9 is coming
Who remembers this little guy:

This is the Open Systems Interconnect model for software on the internet, and it no longer tells the whole story.
Over the past several years, an 8th layer has emerged and stabilized: the social communication layer. Twitter, Foursquare and Facebook have become de facto standards for interconnecting the ‘open systems’ that we call people.
With LinkedIn’s IPO this week, lots of people are saying it’s the dawn of a new era for innovation and creation of value on the internet. There has been lots of discussion and speculation on what’s coming next.
I look at my smartphone, and what do I see? Instagram, Hashable, PicPlz, Tumblr, soundtracking, BlipSnips. I see utilities that are built on top of the 8th layer. The next big thing on the internet is going to be the standardization of layer 9. Just like TCP/IP standardized 4 & 5, Unicode standardized layer 6, HTTP standardized layer 7 and Twitter standardized layer 8, the standardization of layer 9 will yield the next generation of super companies.
So what’s it going to look like? It’s anybody’s guess. I have some ideas, but those are for other posts. I just wanted to take a minute to get my thoughts straight on the matter, and pose the question to you: What do you think layer 9 is going to look like?
Twitter fights: more fun than gchat fights.
This is a pretty neat use of twitter
2500 tweets… someday, @pugofwar
“Open Source Software” isn’t about source code
While thinking about the slides for my upcoming talk at Mongo Boston, I had an interesting thought. It’s nothing earth shattering, but I wanted to write it down and see where it took me.
Lets take a look at the open source ecosystem surrounding MongoDB, and for this example we’ll focus on the Ruby space and some of the stuff I’ve played with at Punchbowl. You have MongoDB itself, which is written in C++. There’s MongoMapper, an ORM. There’s Rack-GridFS, a Rack middleware for directly accessing files stored in GridFS. There’s OpenIDAuthentication, a library for doing OpenID auth in MongoDB. There’s Roachclip, a plugin I wrote for MongoMapper which combines the fun of Thoughtbot’s Paperclip image processing with the ability to store all the assets in GridFS through Joint. There are literally hundreds of open source software projects out there that anyone can pick up and use in a hobby or in a business.
Some of this software has documentation. Some doesn’t. It’s all open source, though. So you can download it, crack it open in a text editor, and just go figure it out. See a problem or notice a lack in functionality? Most of this software is using version control (hi Github); just fork and fix it. What used to be:
http://github.com/original_author/sweet_repo
now becomes:
http://github.com/you/sweet_repo
Maybe your contributions will get pulled into the mainline, maybe your version will remain a fork and start to get used by others, or maybe nobody else will ever use it but you.
Such is the life of open source source code. In my opinion, it’s pretty damn cool. But this coolness is NOTHING compared to what open source is really about.
What I’ve started to realize over the past year is that “Open Source Software” isn’t about the last part of the Github URI: the repository name. Open Source Software is really about the second to last part: The Author.
Open Source Software is about the people. MongoDB isn’t just a C++ repository; it’s Kristina, Mike, Kyle, Dwight & Elliot (among others). MongoMapper, OpenIDAuthentication, Rack-GridFS, Roachclip & Paperclip aren’t just Ruby libraries; they are John Nunemaker, Brandon Keepers, Blake Carlson, yours truly & Jon Yurek (again, among others).
There is obviously value in the code: it does stuff. The code can also teach you stuff. The code can show you how to properly build shareable, modular and properly tested pieces of software. The code can teach you the black arts of meta-programming and the Ruby object model.
But I assure you that no matter how much awesomeness is in the code, there is at least 7 times more awesomeness in the brains of the people who built it. Those people who first had a need for it. The people who struggled through the bugs. The people who had a dozen false starts that might not get reflected by the current HEAD. That experience is PRICELESS. And it’s all available if you just ask.
So, ask. Say hi.
Every single one of those people, and countless more, are “Open Source”. You can get at them on mailing lists, IRC, and Github Issues. You can email them directly or tweet at them. Most of the time, they’ll answer (and don’t get pissed if they don’t answer — sometimes people get busy).
So if you are using Open Source Software just for the source code, you’re missing out. Use these people. Ask questions. Get a conversation going. That’s the real meaning of Open Source Software.
Compete.com thinks twitter.com is shrinking
I don’t believe it.
The best email I have ever received from Twitter — re: Jessica Biel
