Four Years of Coding with AI
Back to blogFour years of coding with AISep 20, 2026 - agents, infrastructureIn 2022, every line of code I shipped passed through my own hands. Four years later, most of it is written by agents on machines I rarely touch, and this is how that happened, one change at a time. Manual coding In 2022 the whole setup fit on one laptop: an editor, a repository and a browser tab open to the documentation.
- ▪Back to blogFour years of coding with AISep 20, 2026 - agents, infrastructureIn 2022, every line of code I shipped passed through my own hands.
- ▪Four years later, most of it is written by agents on machines I rarely touch, and this is how that happened, one change at a time.
- ▪Manual coding In 2022 the whole setup fit on one laptop: an editor, a repository and a browser tab open to the documentation.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,863 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 | Av |
| Canonical URL | https://av.codes/blog/agentic-setup/ |
| Publication time | Tue, 29 Sep 2026 15:35:37 +0000 |
| Retrieval time | 2026-09-29T15:42:01.600Z |
| Last seen | 2026-09-29T15:42:01.600Z |
| 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 | knNW4-ZluvYN · 1 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
Back to blogFour years of coding with AISep 20, 2026 - agents, infrastructureIn 2022, every line of code I shipped passed through my own hands. Four years later, most of it is written by agents on machines I rarely touch, and this is how that happened, one change at a time. Manual coding In 2022 the whole setup fit on one laptop: an editor, a repository and a browser tab open to the documentation. Every line of code went through my hands.The routine was old and familiar. I read the docs, wrote the code, ran it and searched for whatever error came back. The browser was already part of the work, though nobody would have called it a collaborator.ChatGPT arrives ChatGPT showed up late that year, in the same tab bar as everything else.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Av.
Discussion
0 commentsMore from Av
