A frontend veteran maps what to delegate to AI after six months
11/06/2026 — 11/06, 18:18·1 sources (all)·1 reports (all)
Key takeaways
- A developer with eight years of frontend experience reflects on six months of delegating work to AI. Regex, legacy compatibility code, stack…
Background & analysis
On November 6, 2026, a developer who says they have spent 8 years as a front-end engineer at a small company posted on V2EX under the title about handing work over to AI for the past half year. The company has no front-end team at all — just this one person, who owns three client platforms, builds, releases, and middle-of-the-night alerts. Over the past six months they say they have started giving every task that can be delegated to AI, and the post frames itself as practical notes rather than hype.
The tasks that genuinely work well, in their account, all share one feature: they have a standard answer. Regex and legacy compatibility code that used to cost half an hour and ten trial runs now take about two minutes, and after a quick check the result is usable. Last quarter, an old table page from about ten years ago needed an export-to-Excel feature, and AI wrote the whole xlsx section, which took only two style fixes before shipping. Minified error stack traces, pasted in, get roughly located and save about half the usual searching time. Writing comments, documentation, and technical-explanation documents for their boss is where the savings were largest.
The work that does not work out, they say, is exactly what fills their daily job. Whether a field can be deleted depends on a customer from three years ago whose data relied on it — information that lives in human memory, not in the code. The ugly parts of legacy code were written that way deliberately to work around some past problem, and an enthusiastic cleanup by AI means the site breaks in production. At release time, AI does not sign off. When the boss asks for something to look more premium, AI is just as confused as anyone.
At present they explicitly exclude four categories from AI work: payments, permissions, data deletion, and live hotfixes. They also describe an unease that goes beyond productivity: they used to deliver one page a week, which their boss considered normal, but now a colleague using AI can produce three proposals in a day, and the boss comes back asking why they are so slow. Their sense is that AI did not announce that anyone was out of the game; it simply raised everyone's expectations by one notch, and small companies feel that shift most acutely. The post was still in the discussion stage, with roughly 85 views, and the account reflects their personal account as of that date. Other developers' views and takeaways remain to be seen.
AI-generated from 1 reports · updated 1 hour ago
- Heat index
- 96
- All sources
- 1
- All reports
- 1
- First seen
- 2 hours ago
Reports on this story headlines open the original
A developer with eight years of frontend experience at a small company says he has spent the past six months handing AI the work that has a standard answer: regex, legacy compatibility code, decoding minified stack traces, and writing comments and docs. He still keeps the judgment calls himself, and currently refuses to give AI payment, permissions, data deletion, or live hotfixes.
V2EXAI score 54
Other stories people are talking about
- Heat index 1112RisingOpenAI rolls out GPT-6 Cyber to Daybreak Red users with API, Codex access16 sources
- Heat index 762Gemini Omni 1.2 Flash enters Gemini API with video clip extension to 30 seconds11 sources
- Heat index 576Anthropic launches Claude Personal Finance with read-only Plaid bank links9 sources
- Heat index 566OpenAI pushes to make data center commitments legally binding10 sources
- Heat index 496RisingCat Wu joins OpenAI to lead core products10 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

