Hi, Change hurts. The sentence is somewhat jaded. But it became clear to me again a few weeks ago. Toni, an external DevOps Engineer (shoutout to you 😉), was new to the team. On his website he writes, “As an expert in Developer Experience, my goal is to create an ecosystem for high-performance & innovatively-acting development teams.” And he lives it. There is also more than enough to do. And we want to tackle it!
Hi, My microwave was broken. So: I need a new one. However, I have a little quirk when it comes to buying anything that’s not perishable. I want to avoid making a bad purchase. I’d rather spend more money once than have to buy a new one in two years. Here, I have to be careful not to fall down a rabbit hole. I can spend hours reading reviews. But what do I even want to compare?
Hi, Do you know the feeling? You turn on a device that you use over and over again. For years. You recognize the sound it makes. The rhythmic “whoosh whoosh whoosh”, when you start the dishwasher. Or the familiar “click” when the oven turns on. Your signal: everything’s working. Carry on! But what if it suddenly sounds different? It no longer meets your expectations? That’s exactly what happened to me with my microwave.
Hi, “The VPN should not be operated by you [Sysadmins].” After this sentence, I saw startled faces. It slipped out of me. During the weekly Jour Fixe between the developers and admins. It came to the question of what our priorities are. It hit a nerve. Probably not because the participants are emotionally attached to the VPN. Probably not because the statement is wrong. No - it’s more likely because it’s so unconventional for the team.
Hi, What distinguishes an application from a (mathematical) function? A function takes an input x and transforms it into an output. If f(x) = 2 * x, then the result of this function for the input of any x is always the same. There are no side effects. We call this behavior stateless. But what does this have to do with the question from the beginning? An application goes beyond this. (Almost) every application must work with state. As soon as we have I/O operations in our system, we inherently have state. And often a method call, with the same input, can yield different results at different times. And this is also unavoidable and is in the nature of the task we want to solve.
Marcus Held