Creating Multi-Language AI-Powered Apps w/ Rust, Python & Blazor | TJ Gokken

Let’s do some polyglot programming. We’ll create a modern system diagnostics tool called HAL (Hardware Assistant that Learns). We’ll combine Rust’s system-level performance, Python’s AI capabilities with AutoGen, a multi-agent framework, and Blazor’s modern web interface into a cohesive application.

Key Takeaways: Inter-process communication between Rust, Python, and .NET Understand when and why to use different languages in AI applications Learn to implement Microsoft’s AutoGen for multi-agent AI systems

00:00 | Introduction – What is Hell (Hardware Assistant that Learns)?

02:45 | The Project Idea: Improving System Performance with AI

03:20 | Why Rust: Memory Safety and Bare-Metal Performance

05:48 | Why Python: Simplicity, Ecosystem, and AI Libraries

06:48 | Autogen: Microsoft’s Multi-Agent AI Framework

07:05 | Blazor for the UI: A .NET Developer’s Favorite

09:58 | Demo Part 1: Collecting System Data with Rust

12:10 | Demo Part 2: Running AI Agents with Python & Autogen

16:12 | Demo Part 3: Blazor UI with AI Recommendations

18:29 | Automating Builds with Microsoft Aspire

30:50 | Debugging Errors: Lessons Learned

37:50 | Q&A and Final Thoughts

About SSW: https://linktr.ee/SSWTV

Get in touch: TJ Gokken – SSW Marketing & AI Specialist About:
https://www.linkedin.com/in/tjgokken/

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

#RustProgramming #PythonAI #Blazor #Autogen #SSWTechTalks #SystemDiagnostics #AIFrameworks #MicrosoftAspire #aiintegration

V1 – Marcus

About the speakers

TJ Gokken

Enterprise AI/ML Integration Engineer building scalable solutions across platforms. Bridging traditional software systems with modern AI. Writing about practical ML/AI integration patterns at tjgokken.com

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!