How to Read Source Code: Interfaces and Abstract Classes | Luke Mao | SSW Rules - SSW TV - Learn from Professional Software Developers

Master the art of reading source code in our series! Imagine you have a jump into a project and need to understand what the code does. Luke Mao will teach you which parts of the code you should read and how to read them. Today’s topic is Interfaces and Abstract classes. Let’s get started.

00:00 | Introduction

00:28 | Agenda

00:46 | Why Interfaces and Abstract classes are important

01:20 | What Interfaces and Abstract classes are

01:53 | Interfaces example

03:15 | Abstract classes example

04:29 | When to read Interfaces and Abstract classes

05:17 | Summary

Links:

Rule: https://ssw.com.au/rules/read-source-code

Need help?: https://www.ssw.com.au/consulting

LinkedIn: https://linkedin.com/company/ssw/

Twitter: https://twitter.com/ssw_tv

Facebook: https://facebook.com/SSW.page

Instagram: https://instagram.com/ssw_tv

Tiktok: https://www.tiktok.com/@ssw_tv

Get in touch:

Luke Mao – SSW Software Engineer

About: https://www.ssw.com.au/people/luke-mao/

LinkedIn: https://www.linkedin.com/in/luke-mao/

For more information about SSW’s consulting services, please visit https://ssw.com.au/

v7 – Sofie

About the speakers

Luke Mao

Software Engineer at SSW with more than 4 years of development experience. He has a broad technology stack and is especially good at using React for web development.

He has rich experience in remote cooperation with overseas teams. He has worked on large-scale Real Estate projects in Australia and Healthy Living projects in Singapore. He has experience in the fields of Finance，Big Data and Logistics.

In software development, he values code quality, pursues technical depth, and loves Agile. He focuses on high quality and quick delivery to maximize clients’ values.

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!