Having spent the last four years rolling out a handful of service oriented architectures, some lessons are finally coming together, and this is an attempt at documenting them.
One of the fundamental pieces of infrastructure for an effective software engineering team is their deployment pipeline. Here we cover a fairly basic but effective pipeline for deploying code.
After a couple years with the old look, I took some time over the weekend and moved the blog over to Bootstrap.
In management we often find ourselves balancing the freedoms of the few against the freedoms of the many. This is, as you might imagine, a tricky business.
A simple implementation of the war card game in Python, made for an interview some time back.
I spent a couple of hours reading up on and working through an example project using RethinkDB, and it seems like a great tool, as long as its performance and scalability stories prove themselves out with large scale usage.
One of the most destructive ideas is that you can dig out of a hole by doing what you're already doing, but doing it harder. This doesn't work, but it does breed and kill your heroes, and alienate everyone else.
As the SocialCode engineering team pursues building technical leverage, one of the ideas we've been exercising is configuration driven behavior. This post discusses what configuration driven behavior entails, and why we think it's a useful idea.
As part of a toy project I'm playing with I needed to extract titles, summaries and images, so I threw that together as the extraction library.
When things get bad, people start complaining about percieved social hierarchies. Few things piss off the already angry engineer like knowing they're less important than an architect.
Software engineer, technical leader, sci-fi reader, and so on. Born in NC, living in SF, and glad to grab a coffee.