Close to 9am. As it is: Take down a machine for maintenance. Make machine come up again for regular service. Routine operations. (Unless it doesn't. That's where stuff usually gets a bit messy. All too often, complexity gets noticed only when it gets into ones way. And all too often, one wishes to have known things a little earlier.)
9am and on. The usual map of charted rocks and unfound quicksand that guides through the day. Wondering to get out and fetch some actual cookies, for there have been enough digital ones by now, and most of them didn't taste very good. Still somehow in between, today.
9am and going. Still wrangling communication. And bug reports. And users not trained enough but annoyed enough not to care about providing details at all. And technical people making conclusions way too early. Which fixes the wrong things and breaks others even more. (Muting oneself and listening. Watching the winter storm in distant trees. And enjoying the fact that todays coffee is still hot.)
9am and on. Re-learnt: Yesterdays code is legacy today and burden tomorrow. No matter where one's heading, complexity gets into way, and adding complexity just makes that problem bigger. (Muttering and digging through layers and layers of abstract classes cross-referencing each other back and forth. There's still snow frozen on the roofs, world outside the windows is bright white and in a way this feels calming for a short moment, despite the cold and the ice.)
3pm and on. Of tasks and language: Trying to find better wording for environments in which bugs and issues aren't supposed to happen. Seems this is more time-consuming than actually getting rid of the problem itself. (Behavioural anomaly is what the model suggested, and maybe for that very moment, the answer has been convincing.)