Code & Tech
Not long ago, I posted a small article called “Why is (there) Kubernetes?". Its content inspired me to create a short presentation trying to answer the questions “What and Why is there Kubernetes?". See below the recording and its summary after.
When people hear that I work with Kubernetes, a very common question is “What is Kubernetes?". I found more useful to answer “Why is (there) Kubernetes?", to paraphrase the original question. “Why” is easier to explain than “what” because you don't have to go too deep in the technical details and there's an added bonus of explaining the purpose of Kubernetes.
There are a lot of very interesting podcasts out there that I like to listen to, as much as time allows me to do so. But I noticed that I don't recall much out of them and I feel the need to go through them again. It would be great if all podcasts came with a transcript, so I can quickly revisit the parts that interest me. Unfortunately, making transcripts to your podcasts can be quite expensive, which is why most authors don't do so or put them behind a paywall.
The main duty of a developer is to build and improve features of a service or a product, either through big-bang releases or through continuous delivery. The second most time consuming activity (besides meetings, of course) in the life of a developer is fixing bugs and eliminating tech debt.
As a developer, my first impulse when the service I’m developing is malfunctioning is to jump right on it and try to fix it. But while I do that, I can’t help thinking about who is affected by it and how bad and if they will notice it. Then there’s the first five to ten minutes of the investigation, when I realise how far I am from finding a solution, yet, I keep thinking “Almost there, almost there!”. Five minutes become twenty and twenty become an hour. In the meantime, users start reaching…