AI Is Turning Engineers into Farmers, Doctors and Gardeners
The article discusses how AI is transforming the role of engineers, likening their work to farming and gardening rather than traditional coding. Engineers now rely on AI to generate code from prompts, which accelerates the development process but often results in unfamiliar code that requires further modification. This shift necessitates a new approach to understanding and changing code, similar to how doctors learn and adapt to complex systems they did not create.
- ▪AI is changing the role of engineers by allowing them to generate code from prompts instead of writing it by hand.
- ▪The generated code often requires modifications, as it is based on approximate prompts rather than detailed specifications.
- ▪Engineers are compared to gardeners, needing to tend to and adapt the code rather than having an intimate understanding of its creation.
2 outlets in our directory ran this story, first to last over 15 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Turning Neets into engineers — Financial Times — World
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 | Aswinmohan |
| Canonical URL | https://aswinmohan.me/ai-doctors-engineers |
| Publication time | Mon, 25 May 2026 18:03:27 +0000 |
| Retrieval time | 2026-05-25T18:07:39.397Z |
| Last seen | 2026-05-25T18:07:39.397Z |
| 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 | r7ryJJFGcbf_ · 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
2026-May-24 AI is turning Engineers into Farmers, Doctors and Gardeners Think about software engineering before 2022. We were building systems from the ground up. We knew how complex systems worked because we were the ones building it. Even if we didn’t have an idea about the entirety of the system, we knew people who we could ask. Even if we took years to interact with the codebase again, a few hours of digging around would bring back the fond memories of its creation. When dealing with legacy codebases, we would experiment, we would observe its results and then make more changes. But every subsequent change was ours, every change would improve our comprehension of the codebase and our command over the codebase.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Aswinmohan.
Discussion
0 commentsMore from Aswinmohan
