Corona has made me realize the current confinement is going to take a while, so why not spend a bit of time and money optimizing my new work setup. Even though I cannot move *out* at least I can move *around* with my new fancy Bluetooth headphones. Still, it took me a bit of time to cobble together some scripts that help make them work the way I like them. To connect my devices I figured out specific quick solutions to connect/disconnect the headphones which reduces some of the headaches.
There seem to be two different kinds of people in the world, the ones for whom hardware just works, and the ones for who it breaks all the time. Over months my laptop worked alright, but under heavy load it became really slow. Usually one writes of these problems to some particularly badly programmed app, but this is the one case where it's really in the hardware (a welcome relief as a software developer). Diagnosing this problem has become quite difficult with our complicated dynamic processors and intelligent macOs magic that switches the real power of your machine as it sees fit.
Since the inception of the web as a non-commercial decentralized oasis of tiny custom sites, we've moved to a much more stream-lined, clean and ultimately commercial web. As with any trend there's also some resistance. In this case it's creatives that create small curated sites to keep the original idea of the web alive. Lately I've delved a bit into this world.
One of my favorite things about development is constant learning. Usually, your whole task consists of figuring out how to get something to work. Afterward, it would be easy to write down the exact same thing once again. Often it's enough to just mill on the problem or consult StackOverflow a couple of times. But to really get into a new subject you have to go deeper. For this I still really like books. Fortunately, I've found a few colleagues that follow the same out-of-time idea. We are conducting a book club regularly where we discuss mostly technical books among ourselves. Reading for a group like this is very different from reading for yourself.
Nearly all IT companies claim to develop software in an "Agile" way. "Some" practices from the original roots of the movement have become standard. Seems to me, many are relatively comfortable with the status quo because it mostly works. I venture many teams find their own sweet spot in all this mess, but there's no overarching big idea like XP, Agile, Scrum or Kanban in the making. Developer (or Programmer) Anarchy is the one exception that proves the rule with a radical new approach more extreme than XP.