Sunil Pai
sunilpai.dev · Personal blog · on HN since 2024
Sunil Pai, a software engineer, writes about coding agents, stateful serverless, and how AI agents fit into software development.
What HN saysHN links it for his thinking on AI agents and the future of work, including a section on what work remains for junior developers.
15HN people shared it
1linked it in comments
19stories submitted
26story points
3 months agolast shared
2024people per year2026
Most-shared posts
- 1Where good ideas come from (for coding agents)5 people · 5 points · first shared 2026 · discussion on HN
- 2The next evolution of serverless is stateful2 people · 5 points · first shared 2024 · discussion on HN
- 3Never Waste a Token1 people · 2 points · first shared 2026 · discussion on HN
- 4Let's talk about a task tracking system for AI agents1 people · 2 points · first shared 2025 · discussion on HN
- 5Call me maybe: AI agents should be addressable1 people · 2 points · first shared 2025 · discussion on HN
- 6The Task Isn't the Job1 people · 1 points · first shared 2026 · discussion on HN
- 7One Document, Two Hands1 people · 1 points · first shared 2026 · discussion on HN
- 8Developer relations after the cheat code machine1 people · 1 points · first shared 2026 · discussion on HN
- 9AI agents are local first clients1 people · 1 points · first shared 2025 · discussion on HN
- 10Full Stack AI Agents – Solving the Decision Problem1 people · 1 points · first shared 2025 · discussion on HN
- 11Every Company Needs a Cassandra1 people · 1 points · first shared 2026 · discussion on HN
- 12Full Stack AI Agents1 people · 1 points · first shared 2025 · discussion on HN
- 13Partial Prerendering for Everyone with Cloudflare Workers1 people · 1 points · first shared 2024 · discussion on HN
- 14Let the Code Do the Talking1 people · 1 points · first shared 2026 · discussion on HN
- 15Startups Need an Asymmetry1 people · 1 points · first shared 2026 · discussion on HN
What HN people wrote when they linked it
threepointone · 2026-01-05
I touch upon this a little in the epilogue section https://sunilpai.dev/posts/seven-ways/#epilogue-ok-but-doesnt-this-mos… I was thinking what work there really is for "juniors" in this new future, and I suspect the answer then that their "job" is to develop the understanding of the codebase, approaching changes from the edges, and learning how to introduce new changes. (very similar to how people would onboard to a codebase pre-llms: by writing tests, doing smaller changes, poking about the code by adding console statements, etc). The good news is that the coding agent is a very good tool to do that as well. I plan on writing more about this soon.