Live data from Hacker News

Switching to Claude Code and VSCode Inside Docker

timsh.org

151–160 of 170 posts

Re: Switching to Claude Code and VSCode Inside Docker

#152

Earlier quoted context omitted.

If you commit the .devcontainer.json and associated files your whole team gets a consistent, local-feeling, environment for free. Containerisation solved the "Works on my machine" gap between local and prod. This is just solving for the same gap between Dev 1 and Dev 2.

Devcontainers don't "feel" local to me, since my CLI tools are not available in them. Think ripgrep or fd, for example.

You could include those as part of the tooling. I have been experimenting with including mise as part of the image and then layer on the extra tools within there. Put all of those steps into the build so it is automatic.

Re: Switching to Claude Code and VSCode Inside Docker

#153

Earlier quoted context omitted.

Yeah, I don't think you deserve the down votes for expressing an opinion (except maybe that it doesn't add a lot to the conversation), but speaking from personal experience, the whole AI coding thing has been pretty amazing for me. I'm technical, I can read code (even write some of it), but actually completing things or getting started on serious projects is really hard: partly because I am not a professional develop…

I swear to you that if you program the way I do you (without any AI tools or even developer tools made after 2005) you will learn 100x more and achieve 100x more

I agree with you that I would learn more - without any doubt. But there is no way that the second part (the achievement) stacks up. Over the weekend, I deployed a .Net Core API application, developed on Ubuntu and deployed on Windows Server Core, that includes a detailed test suite, full swagger documentation and which works exactly as I had hoped. Up to that point, I had never touched .Net Core, nor Windows Server Core. There is literally no way I would have been able to do that without the assistance of AI agents. Maybe you could, but I couldn't.

Re: Switching to Claude Code and VSCode Inside Docker

#154

I have enjoyed running Claude Code in a container. The biggest advantage for me isn't security though, it's how easy it becomes to spin off agents to work in the background. I use a simple script that copies my working directory into a container, prompts Claude Code, and then either saves a planning document locally, or opens a pull request in GitHub for me to review. I quite like this because it makes starting agent…

> I've never seen Claude Code do anything that git couldn't easily reverse, so I'm not that worried about that any more.

I had one agent that installed something with pip and used it to rewrite my git history. It used the wrong flag and what was left was one file. I am glad I caught it before auto-commit and push triggered. It was one of my hobby projects, so not a huge deal. I can't imagine the fallout of this happening in a work environment.

Re: Switching to Claude Code and VSCode Inside Docker

#155

Earlier quoted context omitted.

I swear to you that if you program the way I do you (without any AI tools or even developer tools made after 2005) you will learn 100x more and achieve 100x more

I agree with you that I would learn more - without any doubt. But there is no way that the second part (the achievement) stacks up. Over the weekend, I deployed a .Net Core API application, developed on Ubuntu and deployed on Windows Server Core, that includes a detailed test suite, full swagger documentation and which works exactly as I had hoped. Up to that point, I had never touched .Net Core, nor Windows Server C…

This is the fatal mistake you are making. What does the application in question do?

Do not mistake the mix of technologies you have used with the problem the code solves. One is a meaningful thing to focus on, and the other is something that career underachievers have invented to keep their salaries.

Re: Switching to Claude Code and VSCode Inside Docker

#156
post #85

Earlier quoted context omitted.

Personally I don’t trust running npm/pip/gradle/etc in my own machine. I feel more secure running them in containers or VMs. Some IDEs like jetbrains’ support remote development (it’s not perfect but better than risking my own machine)

Do you feel safe driving in traffic / breathing polluted air / having restaurants prepare your food?

Clown emoji.

Re: Switching to Claude Code and VSCode Inside Docker

#157

If you are a VSCode hater (like me), you can achieve the same thing using the open-source, Microsoft-built, official devcontainer CLI [0], which is exactly what VSCode uses under the hood. You don't get automatic port forwarding with this tool, which includes SSH Agent forwarding, so you'll likely want to pair this with installing SSH into your devcontainers, or using some other tool that does the job. I built a tool…

Oh the gitlab link is really really really cool. I can't express in words how happy I am since I know about iroh and I always wanted to create such a tool myself too but never could figure out iroh.

Now the way I did port forwarding was really wild and really complicated and I think that it might demand a blog post if I am being honest, but yes this project is absolutely godsend. Thanks!!

Re: Switching to Claude Code and VSCode Inside Docker

#158
post #65

Earlier quoted context omitted.

Just tried it... and it says it's client-only, but when I try to run the SSH provider using my Rapberry Pi it says it needs `docker` to be installed on it :/. So it's not just client-only, is it?

Isn't that what client-only means?

Like, oh you need to install this extremely heavy tool on your server... but yeah it's still client-only, trust me?

Re: Switching to Claude Code and VSCode Inside Docker

#159
post #158

Earlier quoted context omitted.

Isn't that what client-only means?

Like, oh you need to install this extremely heavy tool on your server... but yeah it's still client-only, trust me?

No, client-only as in this is the client only. You need a corresponding server. Are you thinking of "runs locally"?

Re: Switching to Claude Code and VSCode Inside Docker

#160
post #106

Earlier quoted context omitted.

This is like saying: I can write Swift code using Vim instead of Xcode. Yeah, you can, but that doesn’t mean you should. Note: I use nano/vim daily to read and edit files on my servers. Just not to build complex apps.

Your point is good, I don't mean to undermine it, but because I work in this area I feel compelled to point out that depending on the type of Swift you're writing using NeoVim to write Swift is actually quite pleasant: https://www.swift.org/documentation/articles/zero-to-swift-n...

I'm hoping one day to move from a GUI to a VUI (Voice User Interface), though I still have a soft spot for TUIs. Thanks for the link :)
Post reply on HN