Some unfiltered thoughts on Claude Code

Everyone is right, Claude Code is fucking mindblowing.

dang it can build the code, run it, see an error, and modify the code all itself without returning to me

omg

uhhhhhhhhhhhh. this thing is amazing.

It wrote an ldap client for me

and created users and groups in my actual ldap server

this is unbelievable

It took me longer to set up a test LDAP server than it did to have it write code to connect and sync users and groups

2700 lines of code in less than 4 hours, with tests. It actually works on my real LDAP server.

Product idea 1: patch maintainer

I’m thinking how much more software this will put out into the world. And how much more work it’ll seem like to make an open source project that is all things to all users.

Example: my app manages LDAP users/groups. Config file with users and groups, and some dedicated OUs (think like folders where your users/groups are in the LDAP directory), and it makes the LDAP users/groups look exactly like the config file. Idea is you can keep your users/groups/memberships in git, so your LDAP server has no state. (We made something like this at a previous job as a way to keep people from having access they shouldn’t; we could use git history to tell auditors exactly who had access to what when.)

But right now it’s tied to my LDAP server. LDAP is very configurable, you can keep your users in the “people” OU, or the “users” OU, or the “accounts” OU, or anything you want. They might be of type inetOrgPerson, or organizationalPerson, or just account, or (as Active Directory does) sAMAccountName, etc. LDAP is a “directory”, and using it as a specific user/group database is not standardized.

So for my tool to be useful to the world at large, I would have to make it as configurable as LDAP is. A ton of setup gunk. One way that could go in the new world of Claude Code et al is, I’ll just write this one for me, and you write one for you, and it’s honestly fine because I did this for my fucking homelab on a weekend day between hanging with family and stuff.

But another option is, I could release this open source, and you could have a build pipeline that has Claude Code in there where you tell it “take this code and change it so that it works with my LDAP structure”.

Product idea 2: Infrastructure as Code platform with locally runnable test

Talking to even expensive APIs like OpenAI o1 about Kubernetes is a mess. Claude Code can write the code, test it, read the errors, and modify it in a loop. I saw it do this multiple times. What if an IaC platform enabled this without deploying first?

This would help humans a lot too!

It would also improve editor support - right now VS Code can F2 -> rename a symbol across multiple files, but Ansible and Kubernetes are just string matching, so if you misspell anything anywhere it just fails. I’m imagining something with a whole syntax and type system like a language.

Or maybe the right solution is just a library on some existing language. Use something with an extensible type system.

Maybe Pulumi could turn into this.

What it’s missing is a high level of integration so that testing locally works exactly like deploying to productionn

My project