Daniel Doubrovkine bio photo

Daniel Doubrovkine

aka dB., @awscloud, former CTO @artsy, +@vestris, NYC

Email Twitter LinkedIn Github Strava
Creative Commons License

I get this question a lot. I turned to my friends, HN and Twitter for some advice.

Step 1: Start by using open-source.

This is great advice. Before writing anything in your application, see if there’s an open-source implementation for it out there. This will make your code simpler, cleaner and more maintainable, or at least will expose you to the incredible amount of software written by very smart people out there.

Step 2: Start by fixing typos in someone else’s README.

The hardest part in contributing to open-source is making the initial effort. See a typo? Fork the repo, fix it, make a pull request. This exercises the contributing workflow and creates muscle memory.

Step 3: Extract non-business logic from your application into a library.

Your application could be less bloated with utility code.

For example, pick a file from the lib folder in your Ruby project and extract it into a gem. I’ve done it numerous times with ruby-enum (Ruby), ARTiledImageView (Objective-C) or VMWareTasks (C#).

Step 4: Don’t bloat your application with non-business logic.

Your application is bloated enough. Don’t add anything that’s not application-specific to it.

That utility class you’re about to write? Don’t do it. Make it into an open-source library right away. It seems like more work, but think about it - you’re starting very small, so the test-code-rinse-and-repeat loop is really tight, you’ll be saving time. Code will be more focused and have better interfaces, helping others on your team use it. You’ll have to document what you’re doing, saving future effort and helping your coworkers and maybe even other users of your library.

Other Resources

There’re other resources, groups, meet-ups and websites that help you find an open-source project to contribute to. These are all great! Please link to them in the comments.