https://a4al6a.substack.com/p/stop-using-pull-requests thought provoking

May 22, 2026 · 8:02 AM UTC ·1 min read · 0 reactions · 0 comments · 35 views

TL;DR · WeSearch summary

The article discusses the implications of using pull requests in software development. It raises questions about their effectiveness and suggests alternative approaches. The author encourages readers to rethink their reliance on this common practice.

Key facts

▪The article critiques the conventional use of pull requests in coding workflows.
▪It suggests that pull requests may not always be the most effective method for collaboration.
▪The author proposes exploring alternative strategies for code review and collaboration.

How this story was covered

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

Centre · 2

▪ Stop Using Pull Requests — Lobsters
▪ Cannot see all pull requests [still true after a month] — GitHub

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/xwero/httpsa4al6asubstackcompstop-using-pull-requests-thought-provoking-4p78
Publication time	Fri, 22 May 2026 08:02:53 +0000
Retrieval time	2026-05-22T08:32:01.187Z
Last seen	2026-05-22T08:32:01.187Z
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	wOyrufjq0jPf · 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 === 235303) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } david duymelinck Posted on May 22 a4al6a.substack.com/p/... thought provoking Sign in to view linked content Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.

…

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

Anonymous · no account needed

Discussion

0 comments