I Use AI to Build. I Don't Let It Think for Me.

May 17, 2026 · 12:45 AM UTC ·6 min read · 0 reactions · 0 comments · 14 views

TL;DR · WeSearch summary

The author discusses their experience using AI tools in software development, emphasizing the importance of understanding code before relying on AI. They differentiate between productive coding and 'vibe coding,' where developers may accept AI-generated code without proper scrutiny. The author advocates for a structured approach that involves writing tests and understanding requirements to ensure quality in the final product.

Key facts

▪The author has been using AI tools for software development for about two years.
▪They define 'vibe coding' as a workflow where developers accept AI-generated code without understanding it.
▪The author emphasizes the importance of writing tests and understanding code to avoid potential issues in production.

How this story was covered

3 outlets in our directory ran this story, first to last over 16 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.

Centre · 2

▪ What do yall think of my first build? — r/buildapc
▪ What do Yall think of this? Murder or Not? — r/CryptoCurrency

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

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	DEV.to (Top)
Canonical URL	https://dev.to/robat_das_3c6e956212f6408/i-use-ai-to-build-i-dont-let-it-think-for-me-2mag
Publication time	Sun, 17 May 2026 00:45:01 +0000
Retrieval time	2026-05-17T01:10:19.091Z
Last seen	2026-05-17T01:10:19.091Z
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	qEAgKWGNCWBF · 3 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)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

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.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3935636) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Orvi Das Posted on May 17 • Originally published at robatdasorvi.com I Use AI to Build. I Don't Let It Think for Me. #ai #automation #webdev #programming I have been building software with AI tools for about two years now. I ship with Claude Code every day. And I still do not vibe code. Here is why that distinction matters more than people think. The first time I watched someone vibe code, I felt the same thing I feel watching someone drive with their knees. Technically possible.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments