I Don't Vibe Code
The article discusses the author's personal experience with vibe coding and Large Language Models (LLMs) in software development. Despite the hype surrounding LLMs, the author expresses skepticism and shares reasons for not embracing these tools. Ultimately, the author prefers traditional coding methods and reflects on the complexities of programming.
- ▪The author has tried using LLMs integrated into an IDE but found them lacking for more complex tasks.
- ▪A lack of willingness to pay for ongoing AI services influenced the author's decision to revert to traditional coding.
- ▪The author emphasizes the importance of experience in programming and the complexities involved in software development.
2 outlets in our directory ran this story, first to last over 2 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ I’m a Normie. Can Normies Really Vibe Code? — Longreads
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 | jacobharr.is |
| Canonical URL | https://jacobharr.is/personal/i-dont-vibe-code |
| Publication time | Wed, 20 May 2026 16:56:42 +0000 |
| Retrieval time | 2026-05-20T17:05:02.733Z |
| Last seen | 2026-05-20T17:05:02.733Z |
| 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 | n-ULjQSaOCsK · 2 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
March 05, 2026 A "brief" accounting of various reasons why vibe coding has just never clicked for me personally as a developer. There has been a lot of discussion online lately about vibe coding and and how Large Language Models (LLMs) will revolutionize the field of software development. Every new model will launch us into realms of pure productivity, shipping software at the speed of thought and removing all the friction and overhead of product development. Or something like that. Maybe. I’ll have to take your word for it. I don’t vibe code. If it’s working for you, great! I’m not really here to argue the merits or flaws of LLMs at depth here in this piece, but it’s just never clicked for me personally. This page is a “brief” accounting of various reasons why.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at jacobharr.is.
Discussion
0 commentsMore from jacobharr.is
