Use AI to make code better
Use AI to make code better If you write code for a living and you aren't your own boss, there's a solid chance by now that you are using AI-powered coding tools somewhere in your workflow, whether you want to or not. There's also a decent chance that someone in your org thinks that "bots write code" means "coders get more done, faster" despite plenty of evidence to the contrary. Agents can indeed write code faster than most devs, but most of the time it's kinda shitty code.
- ▪Use AI to make code better If you write code for a living and you aren't your own boss, there's a solid chance by now that you are using AI-powered coding tools somewhere in your workflow, whether you want to or not.
- ▪There's also a decent chance that someone in your org thinks that "bots write code" means "coders get more done, faster" despite plenty of evidence to the contrary.
- ▪Agents can indeed write code faster than most devs, but most of the time it's kinda shitty code.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,858 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 | Joshmock |
| Canonical URL | https://joshmock.com/post/2026-08-use-ai-to-make-code-better/ |
| Publication time | Wed, 05 Aug 2026 14:56:42 +0000 |
| Retrieval time | 2026-08-05T15:15:44.720Z |
| Last seen | 2026-08-05T15:15:44.720Z |
| 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 | Z5Y8kq9WwogY · 1 stories |
| 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
Use AI to make code better If you write code for a living and you aren't your own boss, there's a solid chance by now that you are using AI-powered coding tools somewhere in your workflow, whether you want to or not. There's also a decent chance that someone in your org thinks that "bots write code" means "coders get more done, faster" despite plenty of evidence to the contrary. Agents can indeed write code faster than most devs, but most of the time it's kinda shitty code. As a person who has written lots of shitty code over the last 25 years, I feel pretty qualified to make that judgment. Shitty code slows developers down, and slows software down too. It introduces bugs that are hard to find and performance regressions that take serious effort to unravel.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Joshmock.
Discussion
0 commentsMore from Joshmock
