SSW TV recorded this years’ DDD conference in Melbourne.

In this video, Damian Brady – a Solution Architect for Octopus Deploy – tells us you should be focused on ‘API first’ when developing your application.

From the presentation description:

Good developers try to make their jobs as easy as possible. We know our application will evolve, so we try to make future changes as simple as possible by layering and decoupling our architecture up front. That’s great, but can we do more?

In this session, I’ll do my best to convince you that an API should be the most important part of your application. By focusing on the API first, you’ll reap huge benefits in support and bug fixing, and you’ll open your application up to nearly limitless new features with minimal effort.

We’ll look at some applications that expose great APIs, and what benefits they’ve seen as a result. We’ll examine the practicalities of an API-first design, and how to avoid some of the common pitfalls. Finally, we’ll put all this into practice and write a demo app – API first.

Take the poll!

Does your application provide an API?

About the speakers

About the speakers

Mr API

Damian is a Microsoft MVP in Application Lifecycle Management and a a Solution Architect for Octopus Deploy.

He is the co-author of Professional 'Team Foundation Server 2013 from Wiley. He runs the Brisbane .Net User Group, and the annual DeveloperDeveloperDeveloper Brisbane conference.

He spends a lot of time training teams on how to improve their software, be it through improving their agile process, devops, or code quality. Damina is a regular speaker at conferences, User Groups, and other events.

Related videos

Related videos

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!

SSW TimePro – Create a new tenant | Jeoffrey Fischer

Learn how to provision a new tenant in TimePro and sync it with an external Dynamics 365 CRM system.