WeSearch

Software engineers are obsolete for now

·6 min read · 0 reactions · 0 comments · 33 views
Software engineers are obsolete for now
TL;DR · WeSearch summary

The article discusses the perceived obsolescence of software engineers due to the rise of AI tools that allow non-programmers to create software easily. The author reflects on their journey as a developer and how the landscape has changed, with everyday people now able to build products without traditional coding skills. Despite concerns about the future of software engineering, some developers argue that those who adapt and leverage AI will still find opportunities in the field.

Key facts
How this story was covered

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

Centre · 1
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Ibrahim Diallo Blog
Read full at Ibrahim Diallo Blog →

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 publisherIbrahim Diallo Blog
Canonical URLhttps://idiallo.com/blog/everyone-is-better-than-you
Publication timeSun, 17 May 2026 18:39:14 +0000
Retrieval time2026-05-17T19:03:20.885Z
Last seen2026-05-17T19:03:20.885Z
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.
Cluster5MYnou_bcp8O · 2 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

Software engineers are obsolete... for now When all the Vibe Coders are beating you! By Ibrahim Diallo Published 3 days ago ~ 6 minutes read Fund this Blog In my first interview for a developer position, I shared a link to my personal project with the interviewer. It was a website for learning how to program. I created it from the ground up. I built the PHP app, designed the database schema, made a nice design to tie it all together. I wrote down my process, and it became the first tutorial on the site. Then I collected tutorials from all over the web and displayed them on my website, which acted as a portal. There was a section for PHP tutorials, for Ruby on Rails, for .NET, etc. Each one individually curated by me. My interviewer was so impressed. I got the job.

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

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

Discussion

0 comments