Common ASP.NET Design Patterns with Steve Smith (Telerik)

In this presentation, Steve Smith, Executive VP of Telerik, discusses Common ASP.NET Design Patterns.

Design Patterns provide common templates for solving the same family of problems in a similar way. They also provide a higher-level language for software developers to use to describe approaches they might choose when designing a component of an application. In this session, you’ll learn about several of the most common, and useful, design patterns used by .NET developers today.

Topics of discussion:

Stages of Learning
Language
Singleton
Proxy
Abstraction
Command
A Tale From the Real World

About the speakers

Pattern Prodigy

Steve Smith is an experienced software developer, architect, speaker, trainer, author, and entrepreneur, with his specialities being in: .NET Programming, Search Engine Optimization (SEO), Internet Marketing and Advertising, IT Training and Consulting, Online Community Building.

He has been developing web-based software using primarily Microsoft technologies since 1997. Steve has operated ASPAlliance.com, one of the largest independent ASP/ASP.NET sites, from 1998-2012. He founded and later sold Lake Quincy Media, the largest Microsoft developer online advertising network. He also founded and later sold NimblePros, an agile consulting studio well-known for expertise as well as their Software Craftsmanship wall calendars.

Steve is an author of several books on ASP.NET and Programming, most recently a contributor to 97 Things Every Programmer Should Know. He has also authored of several software development training courses for Pluralsight, including Principles of Object Oriented Design and many of their Design Patterns courses.

Steve is an Army Combat Engineer Officer veteran - who spent most of 2004 in Iraq leading a platoon of engineers. He was honourably discharged as a Captain in 2005.

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

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!