Ask HN: Is $300/HR too low these days for custom full stack?
The author discusses the challenges of using LLM-generated code for custom full stack development. They express a preference for writing their own code to ensure better understanding and control over the codebase. This approach helps them manage risks associated with debugging and maintaining software in the long run.
- ▪The author aims to maintain client relationships while efficiently completing projects.
- ▪They highlight the risks of relying on LLM-generated code for complex applications.
- ▪The author does not charge for fixing bugs after software delivery, emphasizing the importance of understanding their own code.
Opening excerpt (first ~120 words) tap to expand
My goal isn't to max out hours but to keep clients coming back and get the work done so I can move on to the next thing.Having LLMs write production code for clients presents a lot of extra risk for me in maintaining those codebases in the future. Writing it myself, I know exactly how every stitch of it works, how the logic is delegated, and where everything lives. With LLM-written code for something large and complex, you practically need an LLM to debug it. With my own code, if a bug crops up, I can reliably guess which file and which function out of hundreds is causing the issue.One thing I don't charge for is fixing bugs once software is delivered.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.