Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code's DX is too good. And that's a problem

bharath.sh

Post reply on HN
Print view View original

41–50 of 97 posts

Re: Claude Code's DX is too good. And that's a problem

#41

Post by Trasmatta »

codegladiator wrote: post #29

> With Opus 4.5, Claude Code feels like having a god-level engineer beside you. Opinionated but friendly. Zero ego. Who keeps forgetting variable names and function calling conventions it used 4 seconds ago while using 136 GBs of ram for the cli causing you to frequently force quit the whole terminal. Its not even human level.

And then hallucinating APIs that don't exist, breaking all the unit tests and giving up saying they're an "implementation detail", and over engineering a horrific class that makes Enterprise Fizzbuzz look reasonable

Re: Claude Code's DX is too good. And that's a problem

#42

Post by exe34 »

codegladiator wrote: post #29

> With Opus 4.5, Claude Code feels like having a god-level engineer beside you. Opinionated but friendly. Zero ego. Who keeps forgetting variable names and function calling conventions it used 4 seconds ago while using 136 GBs of ram for the cli causing you to frequently force quit the whole terminal. Its not even human level.

I've been running claude code on a 13 year old potato and it's never used 136GB of RAM - possibly because I only have 8GB.

Re: Claude Code's DX is too good. And that's a problem

#43

Post by philipp-gayret »

codegladiator wrote: post #29

> With Opus 4.5, Claude Code feels like having a god-level engineer beside you. Opinionated but friendly. Zero ego. Who keeps forgetting variable names and function calling conventions it used 4 seconds ago while using 136 GBs of ram for the cli causing you to frequently force quit the whole terminal. Its not even human level.

Context is garbage in, garbage out.

Re: Claude Code's DX is too good. And that's a problem

#44

Post by candiddevmike »

koolba wrote: post #31

> What happened next: Claude installed every CLI, prompted me to login once, then went into autopilot. Configured each service. Ran commands. Checked logs. Auto-corrected errors. Got the app running in minutes. > In another instance, a GitHub workflow was failing. Claude asked if it could SSH into my Hetzner instance to investigate. I said yes. It connected, looked up the config, restarted the Docker instances causin…

And I'm sure just "restarting docker instances" fixed the root problem here...

The maintenance costs here are going to be eye watering.

Re: Claude Code's DX is too good. And that's a problem

#45

Post by nip »

fluidcruft wrote: post #3

I sort of agree with this about cognitive load. I'm somewhat new (started dipping my toes around July) but use Claude code heavily now. I did spend a lot of time playing with configuring it at first and creating agents etc. But I have a weird setup where I have three computers that I work on and at one point I realized vanilla Claude Code had adopted the things I was doing as defaults (and improved on them). So I hav…

> I still haven't figured out MCP or how/why to use them or why to bother. You run servers. I guess. It's too complex for my smol brain to understand

I know this is self-deprecating humor, but you do NOT have a smol brain: MCP servers are not as needed anymore now that Claude Code supports "Skills". They are also very token hungry as their spec is not lazy-loaded like the skills.

It was / and still is very useful if you collaborate with other engineers or want to perform operations in a non-stochastic fashion.

MCP servers are a way to expose a set of APIs (openAPI spec) to an LLM to perform the listed operations in a deterministic fashion (including adding some auditing, logging, etc). LLMs are fine-tuned for tool calling, so they do it really well and consistently.

Examples:

- Documentation / Glossary: MCP server that runs somewhere that reads a specific MD file or database that is periodically updated: think "what are my team members working on" / "let me look up what this means in our internal wiki".

- Gating operations behind authentication: a MCP server that is connected to your back office and allows you to upgrade a customer's plan, list existing customers, surface current. Super useful if you're a solo-founder for example.

Re: Claude Code's DX is too good. And that's a problem

#46

Post by ltbarcly3 »

salomonk_mur wrote: post #35
ltbarcly3 wrote: post #15

"With Opus 4.5, Claude Code feels like having a god-level engineer beside you." Well, not to me or the people I respect. It's getting very good, but it's like having a recent college grad who obsessively reads documentation. Someone with low skill but very high knowledge, often knowledge they are mixing up or not quite getting right. I think if Claude is already 'better' at coding than you, maybe think about going ba…

I had it One-shot the full architecture for a fairly advanced distributed system for a client. It then one shot the actual code design (following absolutely all our our internal requirements on auth, stack to use, security, code styling, documentation, etc). It then one shot (and we code reviewed everything thoroughly) each of the 5 micro services needed. It one shot the infrastructure to use and created the terrafor…

Lol ok dude, good luck with your 'I just resell the output of Claude and I can't tell when it makes mistakes' business model. I'm sure it is a long term valid economic niche.

Re: Claude Code's DX is too good. And that's a problem

#47

Post by bentcorner »

geophph wrote: post #17
MasterScrat wrote: post #4

Earlier quoted context omitted.

How much AI did you use to write up this article? It tripped up my "fake AI-written article" detector a few times despite being interesting enough to read to the end

“Here’s the thing” “The best part?”

"It's not just X, it's Y"

I find it really hard to read articles that use AI slop aphorisms. Please use your own words, it matters.

Re: Claude Code's DX is too good. And that's a problem

#48

Post by gedy »

skydhash wrote: post #18

> With Opus 4.5, Claude Code feels like having a god-level engineer beside you. Opinionated but friendly. Zero ego. > Claude was halfway through refactoring a complex auth flow[...] Then I realized: I'd forgotten to mention that one of those files was also used by a cron job. That is the kind of research you do before you go to refactoring. > Claude Code freed them from "the anxiety of the first step in programming c…

I use Claude and not crapping on it or the boosters, but most of the people who I've encountered in real life who really gush about it, are either semi-technical, and who struggle in some way when coding. Non technical CEO of small startup I was at, manager who didn't go to college, etc.

It's a cool tool! Just am tired of being treated like anti AI because I don't outsource my brain to it, or gush over their DIY UI demos.

Re: Claude Code's DX is too good. And that's a problem

#49

Post by Rikudou »

I wish one day to be so brave to let a tool I clearly don't understand* ssh to a production server with root access**.

* calling it a god-level programmer kinda gave it away they have no idea what's actually going on

** to restart docker containers you either have to be root or part of the docker group which effectively gives you root privileges

Re: Claude Code's DX is too good. And that's a problem

#50

Post by lnbharath »

pico303 wrote: post #34

The example in the article of letting Claude deploy the app worries me. It has me thinking of that line, “AI is really good until you know what you’re talking about.” If the author was clueless of how to deploy the app, how do they know the app was deployed safely or securely? Just this past week I asked Claude for some help with C++ and a library I was somewhat unfamiliar with. What it produced looked great—-if you…

yeah- this is a fair concern and I should have been clearer. I wouldnt do this on anything with real data or production traffic. that hetzner instance was a side project with nothing sensitive on it. the point was more about claudes ability to reason through infrastructure problems not that everyone should hand over ssh keys. you're right to be cautious
Post reply on HN