惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
IT之家
IT之家
B
Blog RSS Feed
罗磊的独立博客
GbyAI
GbyAI
博客园 - Franky
Y
Y Combinator Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Google DeepMind News
Google DeepMind News
博客园 - 聂微东
N
Netflix TechBlog - Medium
博客园 - 三生石上(FineUI控件)
人人都是产品经理
人人都是产品经理
U
Unit 42
博客园 - 叶小钗
Jina AI
Jina AI
MyScale Blog
MyScale Blog
雷峰网
雷峰网
B
Blog
Hugging Face - Blog
Hugging Face - Blog
Blog — PlanetScale
Blog — PlanetScale
Recent Announcements
Recent Announcements
腾讯CDC
酷 壳 – CoolShell
酷 壳 – CoolShell

Stack Overflow Blog

The AI magic words From better privacy to our new ChatGPT plugin, here's what's new on Stack Overflow for Agents AI, JD, and other letters of the law AI cybersecurity is a cat and mouse game Java’s age is its AI superpower Scaling your money safely with AI How to build a secure-by-default AI coding agent Elevating security, control, and accessibility: Stack Internal 2026.6 The economics of agent scale: tokens, ROI, and building platforms for AI-first teams (Part 2) The good ol’ days of building Java When you keep AI Lean, you keep AI correct Inside LinkedIn's cognitive memory agent for agentic personalization Responsible AI adoption needs developer workflow design Dispatches from O'Reilly: The right amount of spec for agentic development Get rid of your CAPTCHA, the future of the web is bots AI Won't Replace Project Managers, But It is Reshaping How Work Gets Done Quantum-Augmented Applications: Integrating Quantum Subroutines into Classical Software Stacks From PHP to team lead of agents: rethinking judgment, review, and data with Google's Andi Gutmans (Part 1) Building an agentic SDLC with a QA engineering mindset What does an agentic SDLC actually look like? No Dumb Questions: What is AI context architecture? Why not just build your own? Solving integration woes with a hackathon Your tokenmaxxing is not valuemaxxing How to be fearlessly AI native Explorers, exploiters, and the myth of the 100x engineer Your MVP doesn’t need a Kubernetes cluster Dispatches from O'Reilly: The best risk mitigation strategy in data? A single source of truth What happens to the internet when robots act like humans? Your trusted knowledge layer: Introducing Stack Internal's new platform experience Developers are attached to tools because tools encode trust
(Re)introducing Developer Story
Philippe Beaudette · 2026-09-11 · via Stack Overflow Blog

I won’t bury the good news here: Stack Overflow is bringing back the Developer Story.

Time for a short history lesson: once upon a time, we had a feature called Developer Story (“Dev Story”)—think of it as a resume or a CV on steroids. It tracked a developer’s career, added inflection points such as new jobs or languages learned, and was generally an all-around useful function to have.

Then, about five years ago, we deprecated this much-loved feature. Many of the most dedicated developers on the site (and on the internet!) expressed their frustration with that choice.

For the past few years, we’ve been looking at ways to bring a little more of the individual developer back to Stack. In short, we've done a great job showcasing your knowledge, but not the people creating that knowledge.

Dev Story is how we fix that.

We realize that people don’t need to come directly to Stack Overflow anymore in order to get answers to their programming questions—the chatbots have that covered. Most LLMs have been trained on our datasets, providing a quick interface to our answers.

But we believe creators should derive value from their work.

And that’s where Dev Story comes in.

It’s a smarter tool built to showcase your true expertise.

Right now, on day 1, we’re supporting what we’re calling “specialties”—these are areas where you have proven expertise, distilled and pulled forward for everyone to see. But we also give you the control over which specialties are highlighted.

Soon, we will also display and report out your non-SO contributions (from integrations with other sites that have verified data about you, as well as from other sites in our own network).

And we’re building it in a privacy-centric way—we won’t be displaying any private info that you don’t EXPLICITLY tell us to display.

And the part that truly excites me: Dev Story will be at the heart of your profile on Stack Overflow, acting as a much fuller picture of your technical identity.

Stack Overflow developer profile page for Stan Davidson, showing 24.3M people helped, 30K+ reputation, and a timeline of achievements.

Dev Story is the foundation of an even broader vision.

This suite of tools is what we’re referring to as “Stack Identity”. It will be the verified developer proof-of-work layer to the internet.

The core concept: your technical contributions should speak for themselves.

You will use Stack Identity to prove and showcase your skills and career. Anyone can list languages on a CV, but your work here, and in places that work with Stack Identity, reveal your true expertise.

Stack Overflow is uniquely suited to deliver this level of verification.

But for now, go check out the Dev Story. It showcases your contributions to the site, who you’ve helped, and how long you’ve been plugging away.

There are places for you to add items to your timeline, to edit your specialties, and more.

One note: your old Dev Story will not be there. Unfortunately, the data for that met the old rm -rf treatment when we discontinued it last time for privacy compliance reasons. We brought the concept back, but we can't sudo undelete the past.

I will caveat this with: this is a “release early and often” feature for us. Our team is making changes on a daily basis and pushing things out frequently. Look for improvements to the specialties tool, integrations with other sites, and new ways to demonstrate expertise.

This is about highlighting YOUR expertise.

So check it out, play with the settings, tell us what you think, and send us your feature ideas!

We're building this platform around the developer community, and we want you involved every step of the way.