WeSearch
When Anyone Can Build Software, Who Decides What Not to Build?

When Anyone Can Build Software, Who Decides What Not to Build?

Younss· ·12 min read · 0 reactions · 0 comments · 10 views
More from Medium programming Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

Artificial IntelligenceProduct ManagementProductivityBusinessSoftware ArchitectureWhen Anyone Can Build Software, Who Decides What Not to Build?Generation is the cheap part. Deciding what deserves to become permanent is not.Younss11 min read·1 hour ago--ListenSharePress enter or click to view image in full sizeThe views here are my own. Reference diagrams, integration inventories, capability maps, target-state decks, standards documents nobody read past page four.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,536 of its stories. Top-voted stories on Hacker News.

Original article
Medium · Younss
Read full at Medium →

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 publisherMedium
Canonical URLhttps://architectureintel.com/when-anyone-can-build-software-who-decides-what-not-to-build-ae07fdb370e4
Publication timeSun, 13 Sep 2026 05:59:26 +0000
Retrieval time2026-09-13T07:16:50.051Z
Last seen2026-09-13T07:16:50.051Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterhnMhFIuRTb4C · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — 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.

Opening excerpt (first ~120 words) tap to expand

Artificial IntelligenceProduct ManagementProductivityBusinessSoftware ArchitectureWhen Anyone Can Build Software, Who Decides What Not to Build?Generation is the cheap part. Deciding what deserves to become permanent is not.Younss11 min read·1 hour ago--ListenSharePress enter or click to view image in full sizeThe views here are my own. The examples are composites drawn from twenty years across several institutions, and none of them describes any particular situation.An appealing assumption is gaining ground: now that generative models can write code, map integrations, and produce technical documentation in seconds, enterprise architecture is an expensive relic of a slower era.Before I argue against that, let me concede the part that is true, because most defenses of our profession skip…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Medium