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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48245259 |
| Publication time | Sat, 23 May 2026 06:31:24 +0000 |
| Retrieval time | 2026-05-23T06:37:24.939Z |
| Last seen | 2026-05-23T06:37:29.326Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | w_o0rpNwOLCZ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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.