your pet project doesn't stand a fighting chance

Developers! Developers! Developers!

Photo of Steve Ballmer from Wired Photostream on flickr

Your project is probably doomed to fail, which is sad because I bet its really cool and/or helpful. Sadly though, it doesn’t matter how incredible you are pumping out the codez; there is far more to a successful project than that. Below are some problems you are likely seeing and how you can improve your projects success. Note: these suggestions are just as valuable in open source as they are in your workplace.

Problem 1: No one is downloading / using your project

Assuming you actually built something useful, the reason that no one is using your stuff is not that its too complex or that you’re users are too dumb to get it (although simplifying always helps). It’s because you’re not doing a good job at convincing them that Pet Project v1.0 will help them.

Think about the last time you heard about a new library or tool and hit the google, only to find no documentation (maybe some rdoc/javadoc if you are lucky, not that they commented on the methods/classes), no screenshots, no screencast, no examples, and hardly even a readme. At this point, you probably just moved on, realizing you didn’t care that much.

If you are making any kind of user interface, take screenshots. They don’t take that long.

If you’re tool/library is sufficiently complex, make a screencast. It won’t take that long. (Without any evidence of course, I think its this fact alone that made things like rails, heroku, and node so popular. Look at that cool video that built something real and deployed it in less than 5 minutes!)

Go back in time (if you’re old enough) to look at PHP conquering the web at a time when every cgi script was written in perl. It wasn’t just that PHP was easier to read/write nor that all the functions were documented online. It was that there were hundreds of tutorials that could concisely show you the php patterns for talking to mysql or reading a file. So write some tutorials. Write a README too. Done right, a README works as a pretty nice tutorial.

People, especially in this highly connected world are lazy. They are bombarded with information 24/7. They don’t have time to figure out your project just to evaluate it. They want to know NOW! They’ll put the time in once you’ve shown them its worth it. You have to “market” your project to compel people to try it.

Problem 2: Your users don’t stick around

Users won’t typically stick around just because you made something. You can’t be a complete dickhead and respond harshly to their emails/bugs. You can’t ignore them. You can’t just put the documentation out there and call it a day. You can’t say, “its open source, submit a patch.” Most people don’t contribute code back. I don’t know why, but even when its clearly spelled out as an option, they just don’t do it. What people do do (hehe) is ask for help or submit bugs. (They also complain, but whether its twitter or the lunch room, if you are paying attention, you can get the feedback).

So, the question remains, how do you handle this FREE feedback? Do you help the users? Do you write up a FAQ? Do you fix the bugs they report? Do you help them work around their issues (even if it means debugging THEIR code)? Do you plan their improvements and communicate their timeline? Update your wiki?

Its not even enough to do these things every now and then. You have to do them now. If they have to work around your project too much, without your help, they will have no reason to stick with you.

Everyone has an agenda, list of goals, schedules, and goals. If you help someone get to their goals quickly, they will appreciate your help and will probably help someone else with similar issues that they had. This is important for your project, as not only do you keep your users, the users actually start promoting your project in various ways.

Which brings us to…

Problem 3: You don’t foster a community

Its great that you tackled problems 1 and 2 before they even became problems. Pat yourself on the back but don’t start resting yet. If you hadn’t noticed, all of the above takes a lot of time and effort. Luckily, now that you have the users, you don’t need to go at it alone, but you do need to encourage a community so that your users help you.

Of course they’ll tell their friends and boss about how great you tool/framework is. But if you have a forum for help, they’ll probably start helping other users. If you have a mailing list, they will answer questions before you have to. They’ll sit on your irc channel helping people. They’ll help you test out new versions. They’ll be a sounding board for future features. And eventually, they’ll start contributing code.

But you have to foster this. You need to create the mailing lists or forums. You need to link to helpful blog posts from your README. You need to make it clear where to go for support. You need to make it clear how others can help. And if you want help developing, you better write docs on compiling/building/running tests.

You may not always have time to work on your project and as amazing as it feels to be critical to its success, the best thing you can do is make the project resilient to your absence.

Bottom line

All projects have Product Manager(s), Project Manager(s), Community Managers, Support and Documentation teams, Designers, Developers, and QA. One day, when your project is a wild success, various people will fill these roles (even in open source), but for now, as the sole developer of Pet Project, its up to you.

  • #Code
  • #OSS
  • #Success
  • #Thoughts
  • #Tips

My own happiness project

I recently started reading listening to The Happiness Project (Paperback, Kindle, Audible) by Gretchen Rubin and while I would normally be embarrassed to admit I’m even reading this book, I couldn’t help but share it with you due to the immense value its given me so far.

For one, its reminded me that I want to write for my blog more often, thus providing you with this text (even if I am the only one to read it). More importantly, it has reminded me to take time to not only figure out what I want and what makes me happy, but also what makes me unhappy and the nature of my being. Further more, its inspiring me to not only better understand myself, but to accept who that person is and not be afraid to own who I am.

Like Gretchen, I have a short fuse, and like Gretchen, acting on that short fuse snapping makes me feel bad about my reactions long after the snapping is done.

And like Gretchen, there are plenty of things that I wish I liked but in reality, I don’t. To get back into the groove of blogging, here are a few things that I enjoy but don’t do, that I enjoy that I do do (hehe! doodoo), and that I don’t enjoy but do anyway.

things I enjoy but I don’t do (often enough)

  1. working out - I hate going to the gym, but I love how I feel when I’m done. I need to do this more again.
  2. having breakfast out of the house alone with Charlotte (my daughter) - alone time while ‘doing’ something is very rewarding
  3. spending alone time with Spencer (my son) - its time to find something special for just the two of us
  4. reading
  5. working on open source
  6. taking pictures - like working out, inertia is my enemy here
  7. napping
  8. watching documentaries - thats right, I like movies like Helvetica and Jiro Dreams of Sushi

things I enjoy that I do do

  1. making a poop joke every time some says “do do” in a sentence - and just being silly in general, even if its juvenile
  2. listening to audio books during my commute - turns a crappy situation into a manageable one
  3. watching a good football game on a sunday afternoon
  4. going out to dinner with Ceci (alone)
  5. programming - nothing is more rewarding than creating
  6. helping others with their projects - this actually drives me insane at the time but is very rewarding down the road
  7. watching silly “girl” shows with Ceci - housewives, fashion shows, etc. What? I’m man enough to admit it.

things I don’t enjoy but I do anyway

  1. going to the opera - but because my wife enjoys it and I enjoy her company, I can have a good time
  2. reading email
  3. getting up early with the kids - but I do like giving my wife more than 4 hours of sleep
  4. taking out the trash and other chores - seems my wife is the beneficiary of most of the things I don’t enjoy. “Happy wife, happy life”
  5. small talk - I used to think I was extroverted but I’m starting to come to grips with being an introvert that tries hard when he needs to
  6. talking on the phone - I hate the phone; lets do, not talk

I’m sure I could add a ton to this list and maybe one day I will, but for now you have a much better picture of me than you did, and more importantly, I enjoyed writing it.

Thanks, Eric Anderson (@ericlanderson)

  • #Happiness Project
  • #Personal
  • #Thoughts

Making SSH Fast

In my day to day work, I frequently need to bounce to various SSH servers to see whats happening or put out a fire. Nothing drives me more insane than having to wait 5-10 seconds for SSH. So I put together the various pieces in one nice package for you. (Note: this is for mac/linux only)

First, update your ~/.ssh/config to be sure that your Host * section has at least this in it:

Second, add this shell script to your ~/bin or wherever you keep your shell scripts:

Edit fastssh.sh and add new lines for the servers you connect to. In my above example, I have 3 servers defined “jira”, “gerrit”, and “bamboo”.

If you want to provide additional SSH arguments like port forwarding, just add them after the hostname/username.

Finally, make sure you install autossh.

Cool, what does all of this mean?

  • .ssh/config
    • ServerAliveInterval: 30 - Check that the connection is alive every 30 seconds.
    • ServerAliveCountMax: 2 - If there are 2 consecutive keep alive failures, kill the connection.
    • ControlPath: ~/.ssh/master-%r@%h:%p - The location to save persistent connection information.
    • ControlMaster: auto - If there is a persistent connection, use it. If not, create one.
  • autossh - This is a tool, that spawns SSH for you and if SSH quits for an irregular reason, relaunches ssh.

Update: Added explanation of some of the configuration and commands below.

[ Discuss at Hacker News ]

  • #Code
  • #Linux
  • #OS X
  • #Tips

MS Office in the App Store: The Business Perspective

Microsoft, I hope you’re listening. I’m about to outline every business reason in the world for you to be in the app store.

From the Student perspective:

Most students need word processing. Fewer need spreadsheets. Fewer still need to give presentations.

Options: $20-$60 for iWork on the App Store, paid with your itunes account that your parents probably pay for or $150 for MS Office Student Edition.

Winner: Apple

From the Small Business perspective:

Most businesses need word processing and excel. Few need presentations.

Options: $40-$60 for iWork on the App Store or $280 for MS Office for Home and Business.

Winner: Apple

From Microsoft’s perspective:

Best Buy, OfficeMax, Amazon, etc all need to make some profit. From what I can tell from wholesale prices online, most stores will sell you Microsoft products for 15% off. Obviously these companies are still making a profit. I’m guessing that MS sells wholesale at at least 20% off and 30% off wouldn’t be a stretch.

This kills the argument “Microsoft doesn’t want to give Apple 30%”. They give 30% to everyone else for handling their business, Apple would be no different.

But more important for Microsoft is that they are starting to lose the game. There are Macs and iPads in the enterprise. Some companies use Google Docs. The App Store is simple. Its cheap. Unless you absolutely had to get Office, most people will be buying iWork. I can promise you that Apple Store employees will be telling every new Mac buyer that they can get office software for much cheaper in the App Store, rather than buying it in a box from Microsoft.

Options: Continue to have declining business in the Office arena or slash some prices, join the app store, and give Apple 30%.

Winner: I don’t know what Microsoft will choose, but in the first case, it’ll likely be Apple that wins. In the second case, they both win.

Time will tell.

  • #Business
  • #OS X
  • #Random Thoughts

When a computer is not a toy

My first computer was a 33mhz Compaq POS. It has Windows 3.1, DOS, and QBasic. (Side note: yes, I got started ‘late’). After I played my first game in QBasic and realized that the words on the screen are what made the game tick, I was hooked and I have been ever since. I think I tinkered with and hacked every single device I could get my hands on. You name it, if it had a way to get custom software on there, I was going to try it.

This morning I came across an article on Lifehacker about converting your router into a wifi repeater, which sounded really cool to me, so I started reading. Unfortunately about halfway down the page I realized I couldn’t care less about this.

Sure, I can reuse that old hardware collecting dust in the garage. But why? To save a few bucks? What happens when I’m at work and my wife is at home with the baby and the thing stops working? Now I’m getting phone calls to do tech support because I saved $100 and can do that one “cool” thing that I never actually needed in the first place.

When I was 13, the hacky free way was always the best way, not because it was free, but because it was fun to tinker. While it is still fun to tinker, some things should just work. My router should just work. My wife, my mom, and my grandma should be able to use it without calling for help.

The same goes for my phone, my “tablet”, and to some extent, my laptop.

The Android argument that you can install whatever you want and that you can even replace the ROM that runs the phone/tablet is insane. 99% of people don’t need that capability. They don’t need the ability to shoot themselves in the foot. I’m sure it would be fun to hack the OS of my iPhone, but at the cost of possibly not making calls? I don’t think so.

  • #Random Thoughts