Announcing the Blue Collar Coding Company
Today I’m excited to announce a new project: the Blue Collar Coding Company. It’s a natural progression from my junior developer position these past few years.
When I first started at Monax (then Eris Industries) my task was to improve the user experience of the CLI we were building. This was a lot of fun. Along the way, I discovered a knack for writing/maintaining documentation and ensuring repositories were well organized and approachable. Linting eventually appeared on my radar and it was off to the races improving code quality, sometimes uncovering small bugs.
This same work continued once I joined Tendermint/Cosmos. With two GitHub organizations and a growing number of repositories in each, there was much consolidation and streamlining to be done. Then we added linting to the Continuous Integration pipeline. The work is progressing nicely, but here’s the thing: if I do a good job, I’m out of a job.
That’s not all; every software project needs docs/linting/clean repos. However, these tasks are often overlooked, making repositories difficult to approach for beginners. This makes plenty of sense; it is not a good use of engineers’ time to work on these relatively simple and often time-consuming tasks.
Much like a car company, a software project has engineers to design the various parts required for a final product. Unlike a car, however, software is continuously being driven while still under design. Software thus requires regular oil changes, a good cleaning, and an occasional polish. The Blue Collar Coding Company exists to service this widespread need in software today. We do the work your engineers shouldn’t.
The name comes from a Wired article about the future of blue collar work with respect to the growing demand for programmers. There’s a pointed critique that’s worth a read but misses the point. I’ll say this: there is plenty of blue-collar-type-coding-work to go around. Just pick any popular code base and run the linter for its language. Or try the getting started tutorial and find a snag. Most of this work is time-consuming and tedious, but not complicated. And it’s always well received by the maintainers of a repository.
So what am I actually talking about? Below are some links to GitHub Pull Requests that demonstrate these useful fixes. Note that rarely is any code actually written; the focus is on details that improve the overall consistency of code and documentation.
IPFS(open source contributions):
Ethereum (CBC Casper):
These are only a sample of what I’ve been up to keeping repositories clean and well organized. One thing I’ve found quite useful in doing this work are GitHub filters, used in some of the links above. To wit, you can see all the work I’ve done through Pull Requests for a complete overview of the services offered by the Blue Collar Coding Company.