←back to thread

196 points yuedongze | 1 comments | | HN request time: 0s | source
Show context
blauditore ◴[] No.46195811[source]
All these engineers who claim to write most code through AI - I wonder what kind of codebase that is. I keep on trying, but it always ends up producing superficially okay-looking code, but getting nuances wrong. Also fails to fix them (just changes random stuff) if pointed to said nuances.

I work on a large product with two decades of accumulated legacy, maybe that's the problem. I can see though how generating and editing a simple greenfield web frontend project could work much better, as long as actual complexity is low.

replies(16): >>46195970 #>>46195979 #>>46196044 #>>46196111 #>>46196149 #>>46196181 #>>46196747 #>>46197925 #>>46198024 #>>46198073 #>>46198272 #>>46198478 #>>46199426 #>>46200435 #>>46202288 #>>46207763 #
tuhgdetzhh ◴[] No.46196111[source]
Yes, unfortunately those who jumped on the microservices hype train over the past 15 years or so are now getting the benefits of Claude Code, since their entire codebases fits into the context window of Sonnet/Opus and can be "understood" by the LLM to generate useful code.

This is not the case for most monoliths, unless they are structured into LLM-friendly components that resemble patterns the models have seen millions of times in their training data, such as React components.

replies(1): >>46197575 #
manmal ◴[] No.46197575[source]
Well structured monoliths are modularized just like microservices. No need to give each module its own REST API in order to keep it clean.
replies(3): >>46199455 #>>46202013 #>>46203004 #
1. bccdee ◴[] No.46202013[source]
Conversely, poorly-structured microservices are just monoliths where most of the code is in other repositories.