GitHub Codespaces

I think so.

GitHub Codespaces normalized the idea that your development environment lives in the cloud.

CI and CD pipelines normalize the idea that code gets built and deployed in the cloud.

The agent is just the next thing to move.

It's providing that environment, making sure that it's got everything installed.

One of the nice features about Codespaces was that they would do things like pre-builds where you would commit and something would move into main and then they would rebuild the base image so that when you needed to spin up a new one, everything was already pre-installed and it could start up in a couple of seconds.

Because otherwise, if you're having to do your dependency installs and all those kind of things, then it can take a long time to create a new environment.

This takes me back to the point to where I don't need hardware on my desk anymore.

Now it's not anymore the question of your preferences and company's limitations and what's not, but simply it cannot be done.

It was Apple Silicon that really made me question why am I paying all this money for cloud environments? When the M1 chip came out, this was, I don't know, four or five years ago now, that was...

Also, just around the time that there were a load of interesting startups around this cloud IDE concept, and it's when Codespaces first started as well.

And whilst there were these real benefits of being able to very quickly create a new environment targeted to a particular branch, to be able to create and destroy them quickly, they cost so much and the provisioning of them was so annoying to get up and running.

Then we also have nextcloud.com slash developer, where we currently offer tutorials from building your first PHP app to building your first X app.

You can do both either in Codespaces.

So if you're just getting started in development and really just want to get a feel for, is this something I would enjoy? You could use Codespaces on GitHub.

It's free for up to 60 hours a month, so it doesn't cost you anything.

We offer tutorials for that.

It's extra funny because dev environments are with power.

Codespaces.

Well, yeah, yeah.

You were like, oh, I'm so sick of these codespaces.

years ago.

I will admit, I use the dev containers in Docker.

I don't use Codespaces.

I remember back, my first job was consulting environments.

To your point, can you use a remote? Sure.

You still need things to run with NPM, so you're still going to, you know, what, spin up a Codespaces or spin up some Compute.

I can do this on a PC.

And for Mike, I like this feature a lot, but I'm finding my workflow heavily on MCPs right now where I'm not.

What I did was I set up the environment for them so that they know exactly how to do it.

So I used a software called Codespace and a website called GitHub, and then I used another application server called Zavala.

And I set all of that stuff up for them so that they can't break stuff.

And they still break stuff, but the vast majority of the infrastructure took me about two or three months to set up.