Legend Scott Hanselman on what made him successful

var socialJQuery = jQuery.noConflict(true);new SocialBar(“1359511860439_social_6240”, {buttons:[“embed”,”twitter”,”facebook”], badgeUrl:”https://wistia.com”, embedCode:”%3Ciframe%20width%3D%22640%22%20height%3D%22360%22%20src%3D%22http%3A//www.youtube.com/embed/nN-qQiICaBA%3Frel%3D0%22%20frameborder%3D%220%22%20allowfullscreen%3E%3C/iframe%3E”})
In this interview with industry legend Scott Hanselman, Adam Cogan asks some questions to find out what exactly made him so successful in helping the wider community.

Scott works for Microsoft out of his home office in Portland, but he is mainly well recognised and revered by fellow industry folk for his blog, ‘Scott Hanselman’s Computer Zen’, where he regularly posts content that teaches the development community in a number of areas.

In this interview, Adam asks:

What things has Scott Hanselman done, that others can do if they want to follow in his footsteps?
What are the pros and cons of spending most of the time on the community (vs coding)?
What makes his blog different from all the other ones?
The decision to go to Microsoft
Best and worst days at Microsoft
The days of Silverlight – it has its place, for example if HTML 5 can’t do something (i.e. encrypted video) you need a plugin such as Silverlight
How developers neglect physical health in their daily lives
What Scott is going to be doing for the next 5 years

This is a great video because you get to see why being involved with the development community is a great thing for developers, and you learn from Scott some tips on what you can do to better engage the community.

About the speakers

Me Zen

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, and Microsoft employee.

Scott is the creator of the very popular 'Scott Hanselman's Computer Zen' blog, where he provides regular content on wide variety of technical topics to the development community.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!