✳flâneur — a map of the web's best reading
developer relations after the cheat code machine • Solving the decision problem
sunilpai.dev · 1,975 words · saved by 1 readers
(corollary- developer relations is becoming more about helping humans develop judgment around these systems)
developer relations after the cheat code machine 2 April 2026 (corollary- developer relations is becoming more about helping humans develop judgment around these systems) I’ve been thinking a bit lately about what developer relations means right now, and the thought keeps coming back because of a pattern I’ve heard from a bunch of different people over the last few months. educators and technical content creators keep telling me the same thing: engagement is softer, course sales are softer, and people seem much less willing to pay for educational material than they were even a year ago. that’s
Explore this link on the map →saved by
related reading
- The Untrainablex.com
- Your job is to deliver code you have proven to worksimonwillison.net
- Developing our position on AI - Blog - Recurse Centerrecurse.com
- AddyOsmani.com - The Next Two Years of Software Engineeringaddyosmani.com
- We mourn our craft | Read the Tea Leavesnolanlawson.com
- New Junior Developers Can’t Actually Code | N’s Blognmn.gl
- How AI assistance impacts the formation of coding skills \ Anthropicanthropic.com
- I Started Programming When I Was 7. I'm 50 Now, and the Thing I Loved Has Changed | James Randalljamesdrandall.com
- A Coder Considers the Waning Days of the Craft | The New Yorkernewyorker.com
- After Automation | Everyevery.to
- Thoughts on slowing the fuck downmariozechner.at
- The Case for Software Craftsmanship in the Era of Vibes — Zed's Blogzed.dev