tools

Now that I have a century-old house to manage, I’ve found myself struggling to keep on top of all the things that need doing. Not only that, but knowing which need to be done by when, which require tools or parts, and which are on hold can be tricky. To alleviate these problems, I’ve come up with a plan…

There is a lot of talk circulating about the exit of the Air Force and DOD’s first “Chief Software Officer”. Having first-hand experience with the plans, processes, and outcomes allows me to write from a detached observer perspective. What can be learned by those embarking on improving a massive, Brownfield organization?

Coder recently made their enterprise offering free for up to 10 developers. Since my solution, which I will henceforth call “ICSW”, supports 1 developer, it is well within that limit. I configured a new namespace in the same cluster to run the Coder Enterprise system to see how they compare.

TL;DR: Coder Enterprise has a lot of benefits for centrally managed code-server deployments as well as a multi-image workflow.

Upgrading code-server from 3.4.1 to 3.5.0 was always supposed to be easy. Turns out it was easy.

Just for the sake of sharing the ease, I’ve written up the embarrassingly simple process.

The new capability is running additional pods and services (and ingress and statefulsets) within the development namespace using the developer service account. This limited access role can’t impact other services but can start a container and use internal DNS and services to access them.

Pushing the limits of mobility and performance has become easier now that the iPad Pro has the Magic Keyboard and Visual Studio Code can be web-based as code-server.

TL;DR: It’s pretty nice but has some shortcomings. This article covers both the workflow and configuration.