I have been writing code for nearly as long as I have been using computers—which, ugh, it sparks my nostalgic angst fuse to write it but that was in grade school in the nineteen eighties. 

To that point, I have been coding increasingly more and more these last few years, and making more and more meaningful tools in code.

I thought it was high time I started a reflective series of posts on the topic. 

Oh, sure, you can toddle on over to one of my other blogs and read about the intricacies of my coding efforts when I choose to write about them. I am specifically referring to my game development blog where I was for a while simul-writing about the creative processes behind indie game design—but bluntly those posts tend to get into coding and design weeds quite deeply and are not everyone’s cup of joe. 

Code monkey, part one then—and it begins with a wistful reflection on the recent overhaul of my Microfeed Applet. 

Three years ago I was livid.

I was so damn sick of the broken-ass nature of social media I set out to divest myself of participation on the platform which I had once loved and cherished, but which had betrayed my trust: Instagram.  Doesn’t that sound weird, to confess such adoration for a social media platform? Well, it was once a triumphant tool of personal expression and sharing. I could make comics or photos or art and spread them to friends and the world. It was like perfect digital self-publication tool made real and easy.  But those damn platforms do as those damn platforms are wont to do: they blurred the notion of customer and user and suddenly I noticed that I was no longer a customer, but just another user who flailed about in algorithmic hell of lost potential. 

In reaction and protest, I wrote some code to upload my photos and text to my own server: 8r4d-stagram, I called it.  It kinda looked like a rudimentary version of Instagram, which back then was the whole point: if they are going to fuck up their platform, then I can just make my own. I can code personal projects, and it’s not like I was going to sell it so who cares how or who or what I replicated? 

We went to New York a couple weeks later and there I used the new little photo posting system every day to post pictures from our trip. It was clunkier than Instagram, to be sure. Of course it was. It was essentially a home-brewed, web-based, beta-version of a billion dollar platform. It could never compete in real life, but it was good enough for me—and I took a lot of notes on what worked and what didn’t. QA on the fly, on the road.

That was nearly three years prior to writing this post. In those years I have tweaked and improved the tool in fits and bursts, but improved it nonetheless. I have extended it, adapted it, fine tuned it and overhauled the guts of how it worked inside. I have added features, removed some of them days or weeks later, enhanced security, broadened the flexibility and made it work so much better than it did during that trip to New York trial period. 

Code, after all, is one of those iterative efforts. A thing you make might never be done, so long as you can think of new ways of bending and blurring what you are trying to make it do, but then you can update it and improve it. That’s the joy.

I have built hundreds of little programs over the decades, but only a handful have amounted to anything more than toys. My Microfeed Applet is one of those that has become in its own right so much more than a throwaway project.

The last couple of weeks I have put my head back into the code and worked to push it even closer to maturity and even further from a simple Instagram clone. I reskinned the design. I added a menu system. I fine-tuned the back end code that you’ll never see but removes even more of the “clunk.” I refined the usability. All of this is not just in anticipation of another vacation trial period and me taking the tool to Japan to post our adventures in a few months, but because I am an iterative code monkey-type who thrives on continuously improving his tools, sharpening his blade, and enhancing his own skill. I use it. I learn from making it.

And now that I have over a thousand posts on my own faux-social site, every code tweak it makes it easier to keep using it and not go back to broken-ass platforms.