2/13/2026 at 6:49:24 PM
One of my friends and I started building a PaaS for a niche tech stack, believing that we could use Claude for all sorts of code generation activities. We thought, if Anthropic and OpenAI are claiming that most of the code is written by LLMs in new product launches, we could start using it too.Unsurprisingly, we were able to build a demo platform within a few days. But when we started building the actual platform, we realized that the code generated by Claude is hard to extend, and a lot of replanning and reworking needs to be done every time you try to add a major feature.
This brought our confidence level down. We still want to believe that Claude will help in generating code. But I no longer believe that Claude will be able to write complex software on its own.
Now we are treating Claude as a junior person on the team and give it well-defined, specific tasks to complete.
by bakibab
2/14/2026 at 1:18:14 AM
From my experience the biggest difference between AI and junior programmer is that, AI can churn out code very fast, but you need to do the testing and verify the fix. Junior, on the other hand, is very slow in writing code but can do the verification and testing on his own.Usually the verification and testing is the most time consuming part.
I am working on graphical application like AutoCAD, for the context.
by nsoonhui
2/14/2026 at 2:02:42 AM
And the junior learns when you teach him stuff. This is a huge advantage that humans have which LLMs do not have at all right now.by bigstrat2003
2/13/2026 at 11:22:21 PM
I don't think this is much of a problem with the tools rather than with your approach.We have successfully put Claude in huge multi-thousands pr long with projects.
But this meant that:
1. Solid architectural and design decisions were made already after much trial and error
2. They were further refined and refactored
3. Countless hours have been spent in documenting, writing proper skills and architectural and best practice documents
Only then Claude started paying off, and even then it's an iterative process where you need to understand why it tries to hack his way out, etc, what to check, what to supervise.
Seriously if you think you can just Claude create some project..
Just fork an existing one that does some larger % of what you need and spend most of the initial time scaffolding it to be ai friendly.
Also, you need to invest in harnessing, giving tools and ways to the LLM to not go off rails.
Strongly typed languages, plenty of compilation and diagnostics tools, access to debuggers or browser mcps, etc.
It's not impossible, but you need to approach it with an experimentation approach, not drinking Kool aid.
by epolanski
2/14/2026 at 1:56:35 AM
I guess I'd rather just complete one tiny part at a time with Claude and understand the output then do all that. It seems like less effort and infrastructure. And a lot more certain in outcome.by mythrwy
2/14/2026 at 12:17:34 AM
OK, you have a go and show us how its done.These posts are tiresome. Show us something. Go on.
by cxvwK
2/14/2026 at 2:18:23 AM
Is it worth starting from scratch and adding a "make it easily extensible" to the initial prompts? Maybe with the recently released models it'll do an even better job. Just keep rebuilding from scratch every time a new model version is released.by ares623