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 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.

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.

Should you remove data from the database or simply mark it as deleted? At Teem we have a lot of data that we need to manage and often “physically” deleting the data from disk can be problematic. Either the users simply wants to undelete something or the deletion would cause problems for a log. The generic solution to this problem is to soft delete/archive the data by adding a deleted_at timestamp field to the table and then filter all queries to hide rows that have been marked as deleted.

Lucas Roesler

I am senior engineer at contiamo.com and an ex-mathematician. I have worked on web applications, algorithms for image analysis, machine learning problems, and pure math research.

Senior Engineer

Berlin, DE