I Use AI in 2026
The author describes their practical use of AI in software development workflows in 2026, focusing on integrating AI agents into their daily work with tools like Claude Code and speckit. They emphasize structured specifications, code review, and responsible use to maintain code quality in open-source projects. AI is used to generate and test code, but human oversight remains essential for refining output and ensuring reliability.
- ▪The author runs Claude Code in a libvirt VM with restricted permissions for security and isolation.
- ▪They use AI agents in teams for larger features, including coding, reviewing, and testing roles, while smaller tasks rely on hand-written instructions.
- ▪A well-defined spec improves AI output quality, and the author reviews all AI-generated code before submission to avoid offloading work to reviewers.
- ▪Tools like diffity streamline code review by enabling annotated feedback loops with AI agents.
- ▪The author stresses the importance of not pushing unreviewed AI-generated code, citing poor naming, redundancy, and weak tests as signs of low-quality contributions.
Hacker News (Front Page) files mainly under programming. We currently carry 672 of its stories. Top-voted stories on Hacker News.
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 | Github |
| Canonical URL | https://fedepaol.github.io/blog/2026/04/25/how-i-use-ai-in-2026/ |
| Publication time | Tue, 28 Apr 2026 07:57:29 +0000 |
| Retrieval time | 2026-04-28T08:13:18.179Z |
| Last seen | 2026-04-28T08:13:18.179Z |
| 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 | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| 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
How I use AI in 2026 April 25, 2026 10-minute read It’s funny Link to heading I had a draft post sitting in my local repo for a while, where I was about to scream about how AI is overestimated. Well, that post aged pretty badly. I never published it, and looking back at the notes I’m glad I didn’t. So what I’m going to write today will only be about my current workflow and how I actually use AI in my daily work — no hype, no predictions, just what I’ve found useful. My setup Link to heading I run Claude Code with --dangerously-skip-permissions inside a libvirt VM. Running it in a VM adds a layer of isolation I’m comfortable with when giving an agent broad permissions to run commands. My configuration and scripts for setting this up live at clauderunner.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Github.
Discussion
0 commentsMore from Github
