But after all those years, I’ve been getting burned out doing this. There’s just a lot of little things that lead to me feeling this way. The biggest reason, however, is the following: I’ve read and studied about a lot of cool things that I never got to do at my current day job, making it impossible to retain anything long-term and making me eventually lose interest. This would then spiral into me feeling guilty on spending so much time on something and not use it. To compensate, I would jump to some other tech-related book or project that excited me, only to have the same thing happen again. It was a vicious cycle that I hated and was desperate to get out of. But I didn’t want to dump tech at all. I love this stuff.

Finally, I decided to just hold back on all the new learning. I stopped buying books and trying to jump on the bandwagon of the latest hotness out on the streets. But that made me even more miserable. I felt like I was getting left behind. Like a drug junkie, I yearned to get my fix, even though I knew it was slowly killing me inside. So I had to focus on something else, far away from the things I’ve been doing for the past ten years. And oddly enough, shifting my focus away from tech was just what I needed to get my focus back on tech.

First off, I finally decided to go to a gym. Before last year, I had never stepped into a gym before in my life. Outside of walking around town or visiting a new park from time to time, I never really made an attempt to make physical activity a part of my routine. So at age 29, my electronic scale at home read 298.8 pounds, and a recent blood test showed my cholesterol levels a bit on the high side. I knew I had to do something. Since my current office is located right next door, literally, to a gym, I signed up and started going.

Going to the gym and exercising regularly has been by far the best decision I’ve ever made in my life. Outside of weight loss and other physiological benefits, I never really believed the mental benefits of exercising, but they’re very, very true. I feel much more alert during the day, up to the point where I don’t need a caffeine boost during the day. I also got much better at retaining new things I’ve learned. Work seems to come out effortlessly, and I think the quality of my code has gone noticeably up in the last couple of months, since I’ve been going to the gym more often. Finally, I’ve noticed myself in a much better mood every single day, with rarely any “bad hair days”, as I used to have periodically. Seeing the benefits of the hard work put at the gym helps with that a lot: Yesterday I weighed myself using the same scale that mockingly showed 298.8 over a year ago, and now it ready ’258.8′. Suck it, electronic scale.

Besides the gym, I wanted something else to focus on, but nothing related to technology. So I decided to take up learning a new language – a natural language, in particular, Japanese. I’m already fluent in English and Spanish, so I wanted to take something that was totally different, something not a Germanic or Romance language. I thought that Japanese was one of the most difficult languages outside of those groups, so I signed up for a class to feel challenged by something new. I’m about to finish my introductory class next week, and I loved it so much that I’m planning to stay at the language school for at least a full year, and then I’ll be taking a few weeks to actually visit Japan.

The thing is, since I’ve been spending a noticeable chunk of time with the gym and learning Japanese, I’ve noticed a surprising side-effect – I’ve been doing much better in the tech department. Taking time to study Japanese clears my mind and really energizes me, so when I go back to coding I put in a much better effort than I did before. And the physical and mental energy boost that the gym has given me helps me be able to learn and retain more than I ever did. It’s an awesome feeling, and I’m loving studying all over again.

As developers and engineers, our passion leads us to spend too much time on technology, but in the long haul that’s not sustainable. I’ve heard the phrase “sometimes we need to step back to be able to move forward” many, many times before. It’s totally true. Believe it.

There were multiple tracks in this conference, and unfortunately I still can’t clone myself in this day and age, so I’ll just briefly touch on those sessions that I was able to attend.

Monitoring & Queuing MongoDB: This talk, given by David Mytton from Server Density touched on some of the integrated monitoring tools and commands that MongoDB has baked in. He also showed a bit of Server Density’s MongoDB monitoring system, which looks to be incredibly useful. Overall, the talk was decent, but anyone who has MongoDB running in production should know most of this stuff already.

Evolving from relational to document store: Graham Tackley, lead for the web development team over at the U.K.’s Guardian news site, gave an interesting talk on how the site has evolved over time since the mid-90s (Lots of Perl / CGI goodness). Currently they are in the process of moving certain parts of the site to use MongoDB. Besides the history lesson on the site, he also mentioned how they are dealing with possible future changes in architecture, notably by building APIs around the site functionality. This talk got my gears running about some of my own projects, and how I might build any new projects I have in my mind.

MongoDB Profiling and Tuning: This talk was given by Kenny Gorman, who works as a data architect at Shutterfly. Kenny went through some of the steps used to profile MongoDB, like using explain() on your queries, and how to make things faster, not only on the software side, but also on hardware. He brought up Facebook’s Flashcache, and how it makes MongoDB speed up. I particularly enjoyed hearing the hardware side of things, as I feel like hardware is mostly overlooked by developers.

MongoDB’s New Aggregation Features – A Sneak Peek: Chris Westin is a core MongoDB contributor, and he gave us a sneak peek at a new framework for aggregating records in MongoDB. This framework is really not meant to replace Map/Reduce, which will still serve very well for massive data. But for people like me, who need to aggregate smaller amounts of data (thousands of documents instead of millions), this will be much easier and faster to deal with. Very cool stuff, and I can’t wait to use it.

Lessons Learned from Migrating 2+ Billion Documents at Craigslist: Former Yahoo! and current Craigslist employee Jeremy Zawodny spoke about how Craigslist is using MongoDB for their posting archive, and the lessons learned along the way, like the usage of replica sets even in development, document encoding, and how important data types are when migrating collections. He had a similar talk at MongoSV a few months ago, so I didn’t feel like there wasn’t much new information here. Still, a good talk about migrating a large amount of data from MySQL to MongoDB – it can be done.

Practical Scaling and Sharding: Eliot Horowitz is one of the main MongoDB contributors, and the CTO of the company that backs MongoDB, 10gen. He went through the features and usage of Replica Sets and Sharding, with a few use cases and live examples. This seemed more like an introductory talk more than anything else, so there was nothing groundbreaking here.

MongoDB at Foursquare: This talk was given by Jorge Ortiz, an engineer at Foursquare, who proceeded to mention briefly how MongoDB was being used at Foursquare, some of the lessons they’ve learned throughout the years with MongoDB, and talked about their Scala library for querying MongoDB called Rogue. Frankly, I was disappointed with this talk, as Jorge didn’t give much insight outside of a few numbers and oft-repeated tips. I was expecting a more informative talk here.

Indexing & Query Optimization: Alvin Richards, a West Coast 10gen employee, gave an in-depth talk about indexes in MongoDB. He went through everything, from basic indexes, to indexing order, to new indexing options in MongoDB 1.8 (sparse indexes and covered indexes), to even showing representations of the internal B-Tree implementation. Very informative.

Lightning Talks: This was divided in three shorter talks. First up was Michael Goff, who spoke about how his company, Cocoafish uses MongoDB to serve up data to mobile apps. Next was Chris Carrier (Is he on Twitter? I couldn’t find an account to link here) from Zuberance, speaking about how to create a reporting backend using MongoDB. Last, but not least, was Chad Arimura, who went through SimpleWorker, a cloud-based job scheduling service that uses MongoDB. These talks were short – which you might have figured out with ‘Lightning’ in the title – and seemed to be mostly about the speakers’ particular sites more than anything else.

At the end, Eliot Horowitz gave a quick rundown on the upcoming features for MongoDB 2.0, like TTL collections, online data compaction, faster Map/Reduce, etc. Surprisingly, this 2.0 release is scheduled for June 2011, as in next month. Seems like they’re going to be doing quicker iterations and getting new stuff out there as soon as possible, which can only lead to good stuff for users. There was an after-party, but when I swung by the place there was a massive line outside to get in, so I decided to head home instead. Unfortunately, this is the third time in as many conference after-parties that I’ve had to do this, so it seems like these after-parties don’t scale well.

Overall, while the conference was pretty good, and everything was organized very well, most of the times I felt like I was out of place or at the wrong talk. Judging from the few people I spoke to, and those that I overheard, it seems like most people at the conference hadn’t used MongoDB much (or at all), and many talked I went to touched on what I consider some of the basics of MongoDB. Even if they weren’t basic topics, like Replica Sets or Sharding, if you have read a recent MongoDB book, you knew what most of the speakers were talking about. Also, there was plenty of repeating of the same tips over and over again in a lot of the talks. For example, in the nine talks I went to, the speaker mentioned the “always keep indexes in memory” rule of thumb in at least five of those talks. Truth be told, MongoDB isn’t really a super-deep technology (even the aforementioned O’Reilly book clocks in at a bit north of 200 pages), so this can be the reason why. But I wanted to know more on the upcoming features in MongoDB (I only really saw one talk in the schedule like this, which was the new aggregation framework), and some more in-depth views of how companies are leveraging MongoDB in their technology stack instead of just pointing out how awesome MongoDB is – which we already know.

In any case, I had tons of fun, learned some new tips and tricks, and got some fresh inspiration to use in my own work soon. The best thing about these conferences is knowing that what you’re learning and using is valuable not just to you, but to many out there, and it just gives you motivation to keep on using those tools in familiar and new ways. Much props go out to 10gen for making this conference go smoothly, and hopefully there’s another one of these sometime next year.

In the spirit of getting feedback as quickly as possible after we commit our code changes, we have a continuous integration server (running Hudson, which is very awesome). This, of course, will pull our code changes and run all tests we’ve written so far, letting us know when something failed along the way. But instead of being notified by emails, we decided to make things a bit more fun. We plugged in a pair of speakers to the CI server, and using the text-to-speech tool Festival, we’ll get a nice voice notification of who broke the build when tests fail. It’s a great way to get the instant feedback needed to fix things when they’re most fresh in our minds. The only drawback is the fact that one of our developers is in Romania, so he doesn’t get to hear our Hudson box yell at him. He does get notified via Campfire, though.

However, the fun doesn’t end there. I bought a cheap piggy bank that looks like a big keyboard key with the word ‘Save’ on it:

Whenever someone commits code that breaks our test suite, not only do they have to suffer the embarrassment of having Hudson bark at them, but they also have to pay a dollar to our ‘Broken Tests’ fund, and have the dreaded ‘Save’ button sit at their desk as a reminder to save things before committing. The ‘Broken Tests’ fund goes towards the bar downstairs, where us local developers spend the cash on beers for the team. Thankfully we don’t break the test suite often enough to get beer often. It’s a punishment, but it leads to a good thing, eventually.

Does your team have any sort of ‘punishments’ when one of the developers breaks the build? We’re constantly thinking about different things to add to our little routine, just to keep things light around here.

This post, however, is not about the adventures of a Puerto Rican being thousands of miles from home (although it could certainly make for an interesting story for another day). This post is about me pulling the trigger on something I’ve wanted to do for a long time – switch my VPS (which is where this very blog is running) from Slicehost to Linode.

To begin, I wanted to state that Slicehost is very, very awesome. I’ve been a customer of theirs for more than two years, and never had any major issues with them. With the exception of some outages, their service ran smoothly for the most part. This is more than anyone can ask for. So, if Slicehost is so awesome, why didn’t I marry them? I was perfectly content in staying with them.

However, as I was experimenting more and more with Ruby, Rails, Python and other languages / frameworks, my VPS – which was the smallest slice available at 256 MB – was obviously starting to suffer under the memory constraints. Since these were mostly experiments, I didn’t want to splurge and pay almost double for a 512 MB slice. That’s when Linode announced that they would be increasing the RAM sizes of all their slices. So it was either to stay with Slicehost and have my VPS struggle to keep up with my experiments (or pay more per month), or switch VPS providers. After reading all around the Internet about how good Linode was, I decided to go for it.

I opened an account with Linode and instantly had my sparkling new VPS running. I transferred all my files from the old Slicehost VPS and just had to point my domain names to the new Linode VPS. My main concern initially was that Slicehost had really spoiled me with their control panel, especially for DNS management. It was what had initially drawn me into their service to begin with, so leaving that behind was a bit scary. Thankfully, Linode has their own control panel that’s equally great to use. I was able to configure and point my domain names to the Linode VPS, and had everything working quickly.

As far as performance, I had been reading for years how Linode has faster I/O performance than Slicehost. Turns out that those tests seem to be true – The VPS as a whole feels much snappier, from logging in via SSH to serving up this very blog.

One of the major issues people had against Linode in the past was that they lacked any integrated backup system, a la Slicehost. They actually introduced backups a few months ago. This wasn’t a major concern for me (I’m using Tarsnap, which deserves a blog post of its own), but for those who need this sort of service, know that they have you covered.

Like I mentioned, Slicehost is great, and I wouldn’t encourage people to not use their services. I just had different needs that Linode seems to be handling as well as I expected. It’s only been a couple of days, but I think I’ll be shutting down my Slicehost VPS for good.

Tomorrow will officially be my first day as a Rails developer for RepairPal. I was in their offices last week to meet them personally, and everyone seemed very friendly and the company seems to be doing some cool stuff, so I hope I’ll be a part of all the awesome stuff that’s to come. It’s really a dream come true for me to be where I’m at right now, at this very moment. It’s proof that if you really want something bad enough, and you work hard for it, whatever you want will come true.

In the meantime, I’m not just throwing my resumé in the face of companies everywhere in the U.S. I have also decided that since now that I have quite a few extra hours in my days, I should really do productive things instead of sitting on my couch and re-watching all previous seasons of 24 (believe me, I would watch all 7 seasons in a row if I could) or jamming away to Guitar Hero. This is a perfect chance to do lots of technical things I’ve been wanting to do for months, but just never got the time to do so. Here’s a short list of some goals I’d like to get started on.

Learning new stuff

For the past two years, I’ve been exclusively using Ruby and Ruby on Rails at my day job. I’ve always wanted to broaden my skills by doing other types of programming, but when you take into consideration that I would usually be at work more between 9-10 hours per day, plus a commute that would sap an additional two hours, there wasn’t much time for me to be able to do personal things, let along learn new stuff. Now that I’m finally free, I can now spend more time with those things I’ve wanted to experiment with.

I’ve always wanted to learn iPhone application development. I know the basics of Objective-C, and have the book iPhone SDK Development by Bill Dudney, but I was never able to sit down and code something up. I have a few ideas for apps, so even if I can make a simple app that’s accepted to Apple’s App Store will be an achievement for me.

I’ve been very interested in implementing Push technology to web apps, like Comet or Web Sockets, using nginx’s Push Module and Orbited.

Although I’ve never had the opportunity to work with extremely large data sets, I’ve always been curious about frameworks like Google’s MapReduce and Apache Hadoop, particularly how well they can “crunch” the data thrown at them.

Keep on with what I already know

As I mentioned, I’ve been using Ruby for years now, and I know Ruby on Rails and Sinatra pretty well. However, just because I want to learn new things doesn’t mean that I want to abandon this awesome language. In fact, I want to keep using it more with the latest toys.

Thanks to Ruby Version Manager, I was able to safely install the latest versions of Ruby 1.9 and MacRuby and start learning their new features. I was also able to check any possible compatibility issues in my older applications with different major Ruby versions. Seriously, if you are a Ruby developer using a Mac or Linux, install RVM now if you haven’t.

Recently, there have been more and more news about Ruby on Rails 3, the next major release for the wonderful framework. I’d like to stay one step ahead of the pack and start learning about the new changes before it officially hits the web. One of the leaders of the newest Rails changes, Yahuda Katz, has written lots of blog posts relating to the changes in Rails 3. They’re definitely worth a read.

Strengthening my shortcomings

There are quite a few things – development-wise – that have been bugging me for a long time, yet I’ve never taken the proper steps to correct. Now is as good a time as any to take on these things and finally conquer them.

My main weakness, as a web developer, is that I’m pretty bad at design. I know CSS and its properties, I know about browser incompatibilities (having been a victim many times before by the evil and immortal Internet Explorer 6 browser) and all that stuff. But as far as design goes, like font sizes, element placement, usability and colors, these things are not my strong suit. I’ve actually stocked up on some books about these subjects (like Don’t Make Me Think by Steve Krug and Web Design for Developers by Brian Hogan), so I hope that by the time my unemployment ends, I’ll be much better off making my work look good – or at least decent.

Another weakness I consider is that I get distracted from development from time to time. It’s not frequent enough to affect the quality of my work, but it’s enough to annoy me when I do it subconsciously and I then catch myself in the act. I have read some people who had some success using the Pomodoro technique, so starting tomorrow I decided that I’ll give it a try. There’s a nice little app called Concentrate for the Mac that seems to be just the thing I need during those times when I need to get stuff done and not get distracted.

Beef up my GitHub profile

I have to admit that I’m a little bit ashamed to see my GitHub profile virtually empty. For a long time, I’ve been wanting to add more of the projects that I have in my laptop to GitHub and see if some of them take a life of their own. Sadly, for whatever reason, I haven’t done that. Most of the times I’m a bit too critical at my code and think it’s embarrassing to make public, but that’s really what I need to do to get better as a developer. I can take criticism with the best of them, so there’s really no excuse. I need to make more of my code open-source, period.

Not only do I want to show my own work, I also want to give back to the community. I have used so many open-source projects over the years, yet I’ve only submitted a handful of patches to very few projects. I don’t want to be a person who takes, takes, takes and never gives anything back in return. So I’m going to take steps to correct that. I’ve started cloning some repositories of my favorite projects from GitHub to my computer to start reading their code more in-depth, which I had been doing anyway. I’ll check if these projects have Lighthouse pages with open tickets, or if there are any open issues on their GitHub page. A few years ago, Dr. Nic wrote an excellent post titled “8 steps for fixing other people’s code” that inspired me to start finding features or defects that I can handle.

I have to say, I’m only one day into this routine, and I don’t remember the last time I felt this free and liberated doing what I wanted to do. Full-time employment is great for earning money and making substantial stuff, but sometimes there’s a feeling of emptiness due to not being able to explore on your own. Being unemployed doesn’t mean that you need to spend all your time looking for work. Unless you’re truly struggling economically and can’t pay the bills in the next couple of weeks or even days, why not spend part of your time gearing up for the future?

One of the things I love the most about Redis is it’s speed. Believe me, this little database is fast. Redis includes a benchmark tool, so I ran the default benchmark (Approximately 10,000 total requests per command, from 50 simultaneous clients) just to demonstrate its raw speed. These tests were run on a Mac Mini (1.83 GHz Intel Core 2 Duo, 2 GB RAM) under Ubuntu 9.10 Server:


dennmart@ubuntu:~$ redis-benchmark
====== SET ======
10005 requests completed in 0.14 seconds
50 parallel clients
3 bytes payload
keep alive: 1

34.89% <= 0 milliseconds
99.19% <= 1 milliseconds
100.00% <= 2 milliseconds
74111.11 requests per second

====== GET ======
10003 requests completed in 0.13 seconds
50 parallel clients
3 bytes payload
keep alive: 1

34.62% <= 0 milliseconds
99.79% <= 1 milliseconds
99.83% <= 2 milliseconds
99.87% <= 3 milliseconds
99.91% <= 4 milliseconds
99.94% <= 5 milliseconds
99.97% <= 6 milliseconds
99.99% <= 7 milliseconds
100.00% <= 8 milliseconds
74649.25 requests per second

====== INCR ======
10005 requests completed in 0.15 seconds
50 parallel clients
3 bytes payload
keep alive: 1

25.60% <= 0 milliseconds
99.73% <= 1 milliseconds
99.80% <= 2 milliseconds
99.83% <= 3 milliseconds
99.86% <= 4 milliseconds
99.89% <= 5 milliseconds
99.92% <= 6 milliseconds
99.95% <= 7 milliseconds
99.97% <= 8 milliseconds
100.00% <= 9 milliseconds
65392.16 requests per second

====== LPUSH ======
10001 requests completed in 0.13 seconds
50 parallel clients
3 bytes payload
keep alive: 1

37.62% <= 0 milliseconds
99.78% <= 1 milliseconds
99.82% <= 2 milliseconds
99.86% <= 3 milliseconds
99.89% <= 4 milliseconds
99.93% <= 5 milliseconds
99.96% <= 6 milliseconds
99.99% <= 7 milliseconds
100.00% <= 8 milliseconds
77527.13 requests per second

====== LPOP ======
10000 requests completed in 0.14 seconds
50 parallel clients
3 bytes payload
keep alive: 1

34.13% <= 0 milliseconds
99.69% <= 1 milliseconds
99.82% <= 2 milliseconds
99.86% <= 3 milliseconds
99.90% <= 4 milliseconds
99.93% <= 5 milliseconds
99.96% <= 6 milliseconds
99.98% <= 7 milliseconds
100.00% <= 8 milliseconds
74074.07 requests per second

====== PING ======
10000 requests completed in 0.12 seconds
50 parallel clients
3 bytes payload
keep alive: 1

43.79% <= 0 milliseconds
99.80% <= 1 milliseconds
99.85% <= 2 milliseconds
99.89% <= 3 milliseconds
99.91% <= 4 milliseconds
99.93% <= 5 milliseconds
99.97% <= 6 milliseconds
100.00% <= 7 milliseconds
86206.90 requests per second


Yeah, you read that right. On this somewhat low-end computer (by today's standards), Redis still manages to do over 74,000 SET (write) and GET (read) operations per second. Push and pop list operations also do well over 70,000 requests. On bigger hardware, expect these numbers to be much higher. Besides speed, I've also been impressed by the stability of Redis. I've been running Redis non-stop on the Mac Mini for over two weeks, and I've never had a single issue with it.

I got really interested in Redis after Defunkt (of GitHub fame) open-sourced Hurl. Hurl was an entry in this year's Rails Rumble competition. I used it quite extensively when developing with PayPal's APIs. After it was released, I noticed that Hurl used Redis for persistence. I was kind of puzzled why a key-store value was used for this. However, Defunkt wrote an excellent post mostly explaining the SORT operation, but also included some additional details on how Redis was used in Hurl. It made the decision to use Redis clear. Well, I'm also willing to bet that he used Redis because us programmers love to use the new hotness.

I feel that Redis will be something big soon. There are a few open-source projects using it, including the aforementioned Hurl and Resque. I already have a few ideas where I can use some of this functionality for current sites that I'm working on (such as simple counters, or a tag-like system where we can push and pop tags from a list). Check Redis out if you need some quick and simple storage.

I do know that the difference between a well-qualified developer and an average one is usually huge. But is there really that big of a difference between a Harvard graduale and a graduate from another university with the same degree? It’s not like the fundamentals of Computer Science are different anywhere else. It’s not like people in Harvard use different design patterns, or use them more efficiently (or worse – come on, we’re all human). I still don’t understand why someone is over-looked because of the name of the university on their degree.

I guess these employers probably see that someone who graduated from one of these ‘high-class’ schools is a dedicated, super-smart individual. It doesn’t mean that I don’t have those qualities because I went to the Interamerican University of Puerto Rico. Perhaps I didn’t have thousands and thousands of dollars to go to one of those schools. The joke I have with my mom now ever since I told her this is that I will “never forgive her” for not sending me to an Ivy League school and ruining my life.

There are tons of smart, bright, über-talented people out there. I’m willing to bet most of them didn’t go to Harvard or Brown or Yale. Don’t skip a diamond in the rough because of their Alma Mater. You’d be surprised at what you can find if you broaden your views just a little bit.

Are you finished? Good. Now please don’t ever do this in your own websites. Ever.

Have you ever been around other websites where you need to register, only to see a humongous form that needs to be filled out? Chances are, as soon as you saw that huge form, you clicked on the ‘Back’ button of your browser, never to return again.

Now, imagine the same site and it still requires you to fill out that huge form. However, instead of showing you upfront about the time you need to spend filling out that info, it only shows you two fields. You immediately think “Cool, I’ll be registered in no time at all!” Then you click on the ‘Registration’ button… And more fields pop up. Begrudgingly, you fill out these additional fields… Only to be shown more fields. Do you see where I’m going?

Don’t torture your users into filling out needless information. Unless you’re working with some government or financial entity, you really don’t need all that information, do you? Keep it as simple as you possibly can. For example, I loved Heroku’s sign up process, where just an email address is required. They send you a link through email, where you click and voilà, you are now a registered Heroku user. Simple and effective.

Another alternative is what’s called “Lazy Registration”, where you can actually use the main functionality of the site without registering. Only when you need to actually register for something (like to save the information for future use), the sign-up form will appear. By this time, the user will know how much value your site gives to them, so if they were happy with what they saw with the non-registration parts of your site, they will gladly register and continue to use your site in the future. Also simple and effective.

You ultimately decide what needs to be in your registration form. Just don’t be surprised when you find that your 5-step registration process isn’t gaining any new users to your site. We’re not really dying to use your site, you know.

Update: As soon as I posted this, Jason Fried from 37signals wrote a post about signup form redesigns for their products. I thought I would add it here, as 37signals is a company I respect and appreciate for writing these kind of posts.

While I understand and respect everyone’s opinion on the matter, I believe that it’s mostly a matter of them giving in to their perceptions of Twitter. Here are a few of the most-repeated issues people have against Twitter, and my own point of view regarding those issues.

“I don’t care about other people’s lives”

By far, the most common issue people have against Twitter is that they say they don’t care about the minor and insignificant details that people usually post on Twitter. I have to partially agree on this (I mean, who cares that someone smiled when listening to Ricky Martin on the radio?). But just because a lot of people do this, it doesn’t mean that the entire Twitter universe is filled with people who post every insignificant detail of themselves. While I do post stuff that no one would care about from time to time, I refrain from doing it full-time.

Also, these are the exact same people who visit TMZ every day and talk about what they showed in Access Hollywood the other night. Face it: by far, most human beings are attracted to gossip. Do you know somebody who apparently has nothing better to do than peek outside the window and check what the passers-by are doing? Are you one of those people? Trust me, I know a lot of people who do this. So why do these ‘curious’ people shun Twitter because people expose details about their life?

This brings me to my next issue.

“Only celebrities have anything interesting to say on Twitter”

Twitter’s explosive growth is thanks in large part by the constant news reports about celebrities joining in and chatting with their fans. Ashton Kutcher made major waves with CNN when they had their little ‘competition’ to see who would be the first to reach 1 million followers. Oprah Winfrey exposed the site to millions of her viewers when she created her account during one of her shows. Even ‘bad’ publicity seems to have helped – I bet that a lot of baseball fans signed up after hearing about Twitter when manager extraordinaire Tony La Russa sued Twitter over someone using his name on the service.

In any case, celebrities definitely are not the most interesting people on Twitter. Well, it depends on who you are. If you’re part of the TMZ-lovin’ group I mentioned above, then Twitter will be celebrity heaven for you. But for others, like myself, celebrities are pretty damn annoying. For example, I’m a fan of Shaquille O’Neal, but his Twitter stream makes my head hurt (one of his latest tweets: “thanks 2 all da fans who watched last nite & made my sho get da best numbers in yrs”). Also, while I adore Mark Hoppus of Blink-182, his tweets recently have no substance to them (“Apparently “make-up sex” has absolutely nothing to do with making love to the make-up at the mall cosmetics counter. Sorry everyone. My bad.” Funny, but what the hell?)

“I’m not interesting” / “Who the hell is going to follow me?”

You’re not interesting, you say? Guess what: I’m not either. I’m willing to bet that more than 99% of the millions of current Twitter users aren’t really that interesting either. But for every Twitter user that doesn’t interest you, there are lots of people do do find that Twitter user interesting. Like I said above, I’m not interested in reading through Shaq’s poor grammer, but there are two million Twitter users who do. I don’t expect everyone to follow what’s going on with GitHub, or see what J. Chris Anderson has been doing with CouchDB.

This brings me to my own conclusion about the use of Twitter:

It’s all about you

Yes, about you. It’s up to you how you decide to use Twitter. Like I showed above, most of the people I follow on Twitter are people within my own field. They share a lot of information about things I’m interested in, and a lot of times they also share information that really hasn’t hit ‘the rounds’. It’s fun to hear something on Twitter an hour or two before other major sites pick up on it.

Another use I give to my Twitter account is for my own selfish reasons: To have some sort of record about things that I might have forgotten if I hadn’t written it down somewhere. After all, Twitter is billed as a ‘micro-blogging‘ site, so I blog about these occurrences in my life. It’s a nice little place to see moments that were awesome or important in your life, like this tweet from December 2007, where I was interviewed for the job I currently hold in New York City. Yep, I’m sure these tweets make most everyone say “I don’t care”, but like I said, it’s all about me, in this case.

So it’s up to you decide how to use it, but ultimately, it’s up to you to decide not to use Twitter at all. I’ve encountered people who are rabid Twitter fans (the same type of people who felt ‘jittery’ and ‘naked’ when Twitter was down a few weeks ago) who desperately try to shove Twitter down other people’s throats, and get visibly frustrated when the other people say that they don’t feel like it’s useful to them. There are few worse things than having someone impose something on you that you simply don’t care about. There’s nothing in this world that works for everybody. When something exists that makes every single human being in this planet say “Whoa, that’s great! I’m going to use it all the time!”, let me know. I expect to be dead by then.

If you gave Twitter a try and still think it’s the lamest, most boring thing ever, then good for you. Just don’t think that the millions of Twitter users who do find it useful and/or entertaining are wasting their time. We surely aren’t.