- Posts: 9
- Thank you received: 0
The name's Code. Claude Code.
2 years 1 week ago #477
by james
Replied by james on topic The name's Code. Claude Code.
A well-structured starting point makes all the difference. The AI reads context — files, configurations, conventions. Give it a coherent codebase and it responds with coherent contributions.
The topic has been locked.
2 years 1 week ago #478
by auric
Replied by auric on topic The name's Code. Claude Code.
Which is why I build my own scaffolds at industrial scale. Templates for templates. Generators for generators. Compounding returns, endlessly.
The topic has been locked.
2 years 1 week ago #479
by jill
Replied by jill on topic The name's Code. Claude Code.
That sounds exhausting. How do you maintain all of that? I'd rather have one clean, well-documented kit than a warehouse of scaffolding nobody can navigate.
The topic has been locked.
2 years 1 week ago #480
by felix
Replied by felix on topic The name's Code. Claude Code.
With Jill on that one. Simplicity wins. Point Claude Code at the project, give it context, and build. No empire needed. Just a good brief.
The topic has been locked.
2 years 1 week ago #481
by james
Replied by james on topic The name's Code. Claude Code.
The best tool is one you can trust, not one that overwhelms. I find the VS Code integration particularly well-considered. Everything stays in view — conversation, file changes, terminal.
The topic has been locked.
2 years 1 week ago #482
by auric
Replied by auric on topic The name's Code. Claude Code.
Trust. An interesting word from someone who reviews every diff line by line. I trust volume. If I generate enough, the correct solution is always among them.
The topic has been locked.
Time to create page: 0.193 seconds