I recently had a week long battle implementing HTTP long-polling. As so often happens in long debugging session in software development, my final fix was one line!
I had to learn about Go struct embedding the other day and I wanted to document my fix. In my use case I wanted to add some extra information to an API response to include some meta data from kubernetes cluster and/or some extra error information.
At Contiamo I am currently working a project that will eventually integrate with OpenFaaS. I am really excited about this project because we will soon bring some serverless magic to data scientists that use Contiamo. That is, once I figure out how to deploy a private Docker registry inside a Docker Swarm.
At the beginning of the month I left Teem I was Director of Engineering and it was and still is a great company. There are some amazing developers there, so if you are looking for a job in SLC, hit them up. This weekend (Aug 5) I will be moving to Berlin to start a new role at Contiamo and will be working on the Labs feature.
This recipe is inspired by the Seirra Nevada Ruthless Rye Clone written up by the Home Brewers Association. I have adjusted it to be a partial mash recipe with about 8 lbs of grains.
I just finished my first official “summer beer” of the year, an Orange Honey Wheat. This one was inspire by my wife while at the store “you should do this one, it uses Utah honey!”, thank you tech lady ninja.
Ever have that feeling you are forgetting something right as you leave work? You are probably thinking about your keys or your lunch box but I am talking about your SSL certificate. They don’t last forever, we know this when we setup SSL but that doesn’t stop it from sneaking up on us. It has happened to the big guys like Instagram and Google, at Teem recently, and of course for myself with my own home server.
Recently, I have seen several articles talking about RESTful API design. Of course this is also a common topic of discussion for the engineers at Teem. I want to use (and write) APIs that are easy to understand and explain and the fastest way to complicate your API is nested routes. Just don’t do it! Do not create nested routes in your API. Let’s keep our APIs simple and create one endpoint per resource and if filters are needs, use GET parameters. This is simpler to document and simpler to maintain and ultimately, easier to use.