When working with Kubernetes, a question that will always come up is: "how to set up proper health checks"? The Kubernetes documentation provides some basic information about why you might want to use them and how you configure them. But, as with all things–it is a bit more complicated than that.
Every software development team depends on architectural decisions. But more than often, the results of architecture discussions are never written down. This is a seed for future conflicts and software bugs, that can (and will) lead to unhappy developers and broken team productivity in the long run. But it isn't actually too hard to create decision records that are not overly complex or hard to create.
Welcome to the Blog of Tentacle Labs! Recently we got inspired by a post on the StackOverflow blog. It highlights how developers benefit from expanding their skill of writing text, not just source code. One point got us hooked in particular: "if you can't teach it, then you don't really know it."
