--- title: "Agentic Coding: Bet on the Primitives" url: https://daily.dev/posts/agentic-coding-bet-on-the-primitives-rbwr3lrii source_url: https://www.robinwieruch.de/agentic-coding-bet-on-primitives type: article source: "Robin Wieruch" author: "Robin Wieruch" published: 2026-07-31T13:32:55.364Z updated: 2026-08-01T10:00:09.721Z tags: ["webdev", "react", "ai-coding"] reading_time: 8 upvotes: 14 comments: 2 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Agentic Coding: Bet on the Primitives **[Robin Wieruch](https://daily.dev/sources/robinwieruch)** · [@rwieruch](https://daily.dev/rwieruch) · 8 min read · 14 upvotes · 2 comments ## Summary Agentic coding is shifting the economics of software abstraction. Using a real freelance project as a case study, the author ran a head-to-head experiment building custom charts with D3 primitives versus Recharts. The D3 approach matched the design system exactly without workarounds, while Recharts hit a wall at the last 20% of customization. The core argument: high-level libraries were never free — they traded flexibility for implementation labor. When AI agents collapse the cost of writing custom code, the rational choice moves back down the abstraction ladder toward unopinionated primitives your team owns. The post also argues against itself: this bet only makes sense if your team has an agentic workflow, understands the output, and your UI requirements genuinely diverge from a library's happy path. For commodity UIs or deep accessibility needs, mature libraries still win. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@kartiknvj** · 2 upvotes > The D3 versus Recharts case study captures something I keep running into: high-level libraries save you time right up until the last 20% of customization, where they start fighting you. With an agent doing the labor, the old tradeoff of primitives being too much work begins to flip. Betting on primitives makes a lot more sense once typing is no longer the bottleneck. **@agustinbarrientos** · 0 upvotes > Mature libraries carry years of screen-reader and keyboard testing, so I would keep them for accessibility-heavy components. --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#ai-coding](https://daily.dev/tags/ai-coding) [View this post on daily.dev](https://daily.dev/posts/agentic-coding-bet-on-the-primitives-rbwr3lrii)