What's after CI/CD?

I'm still loving CI/CD pipelines. Made some major upgrades on one of my side projects today including adding some filtering so I can push changes back to the server without triggering an update of my "production" environment until I'm ready. 

But, in the process of getting those new features up and running I ran into something else that gets in my way as a developer. Setting up an environment. I had wanted to do the work on the desktop on the main floor. It hadn't been set up yet however, and so a bit of a headache ensued.

And that brings me to the next hurdle to solve. For these projects which aren't in .Net which is my strongest skill, it would be nice to have a ready to run development environment. And, I think I have a way to achieve this.

Which, once again, means that the next big thing in development for me is... not development at all.

Anyway, when I have some time I'm going to look into it. But, I have an image from linux-server.io for a browser based version of VS Code. If I use that as my base image for a Docker file and kit it out with extensions, runtimes, etc... then I should have something that I can either run in one place and access everywhere, or simply build locally in Docker and run that way.

Of course, after thinking on this, it probably shouldn't surprise me that these sorts of solutions are what excite me the most. My favourite things to build are tools after all. So, finding quality tools and processes to use and adapting them to my coding practices SHOULD be exciting. But, I also just kind of generally believe that this should excite developers in general.

After all, I'm not manufacturing problems. These are real things happening to me, in real time. And the solutions are meaningful and effective. And while not everyone's situation is the same. I certainly do think that most developers who have side projects will have run into these issues or will do so in the future.