Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
157055 stories
·
33 followers

Building an AI-Powered Personal Companion Mobile App - Gerald Versluis - NDC Copenhagen 2026

1 Share
From: NDC
Duration: 58:54
Views: 24

This talk was recorded at NDC Copenhagen in Copenhagen, Denmark. #ndccopenhagen #ndcconferences #developer #softwaredeveloper

Attend the next NDC conference near you:
https://ndcconferences.com
https://ndccopenhagen.com/

Subscribe to our YouTube channel and learn every day:
/ @NDC

Follow our Social Media!

https://www.facebook.com/ndcconferences
https://twitter.com/NDC_Conferences
https://www.instagram.com/ndc_conferences/

#mobile #dotnet #ai #crossplatform #microsoft #ui #ux #genai

Ever wondered how to integrate AI into your cross-platform apps?

In this session, we'll explore building an AI-powered companion app using .NET MAUI. We'll harness the capabilities of .NET MAUI to create a seamless user experience across platforms and integrate AI functionalities to make our app smarter and more responsive.

You will walk away with all the knowledge you need to build your own personal Jarvis, whether you want to get personalized book recommendations, crazy roadtrip ideas or get food recipe ideas... After this session you can build it all!

Read the whole story
alvinashcraft
56 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Completing the Rewrite from Hell: Five Years of Technical Debt and How We Escaped - Aaron Stannard

1 Share
From: NDC
Duration: 50:55
Views: 55

This talk was recorded at NDC Copenhagen in Copenhagen, Denmark. #ndccopenhagen #ndcconferences #developer #softwaredeveloper

Attend the next NDC conference near you:
https://ndcconferences.com
https://ndccopenhagen.com/

Subscribe to our YouTube channel and learn every day:
/ @NDC

Follow our Social Media!

https://www.facebook.com/ndcconferences
https://twitter.com/NDC_Conferences
https://www.instagram.com/ndc_conferences/

#architecture #dotnet #continuousdelivery #genai #data

Bad architecture decisions don't just slow you down - they destroy business value. Poor coupling means you can't add the features customers are asking for.

Data model mistakes mean you don't have the information to answer your questions, and a lot of your decisions can't be easily reversed. You know the problems are there. You've known for years. But there's never time to fix it properly - you're too busy keeping the lights on.

Then one day, the stars align. You finally have time to tackle it. You open the codebase, ready to make things right - and realize you have no idea where to start. Everything is wrong. Every fix breaks something else. The whole thing feels impossible.

I'm a business owner. I had full authority to prioritize this rewrite. No one to convince, no budget to fight for. I still couldn't make it happen for five years - even while watching money walk out the door.

This is the story of how we finally completed that rewrite. You'll learn:

- Why we abandoned a full rewrite and pivoted to strategic refactoring instead
- How to assess whether your legacy system is salvageable (ours barely was)
- The architectural patterns - including the actor model - that would have prevented this mess
- How we used AI to accelerate the work (spoiler: it wasn't vibe coding)
- The management failures that let this happen, and how to avoid them

This isn't a talk about how smart we are. It's about how we recovered from one of my biggest failures as an engineering leader - and what you can learn from our five-year journey through hell.

Read the whole story
alvinashcraft
57 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Snowclones: fill-in-the-blank phrases we can’t stop remixing. Plus, is it 'RBIs' or 'RBI'?

1 Share

1200. This week, we look at snowclones like “X is the new Y,” including where the name came from and why we find them so satisfying. Then, we look at how to make abbreviations like “RBI” plural, including questions about apostrophes, single letters, and periods.


The snowclones segment was written by Karen Lunde. Find her on igofirst.org.


🔗 Join the Grammar Girl Patreon.

🔗 Share your familect recording in Speakpipe or by leaving a voicemail at 833-214-GIRL (833-214-4475)

🔗 Watch my LinkedIn Learning writing courses.

🔗 Subscribe to the newsletter.

🔗 Find an edited transcript.

🔗 Get Grammar Girl books.


| HOST: Mignon Fogarty


| Grammar Girl is part of the Quick and Dirty Tips podcast network.


  • Audio Engineer: Castria Communications
  • Director of Podcast: Holly Hutchings
  • Advertising Operations Specialist: Morgan Christianson
  • Marketing and Video: Nat Hoopes, Rebekah Sebastian
  • Podcast Associate: Maram Elnagheeb


| Theme music by Catherine Rannus.


| Grammar Girl Social Media: YouTubeTikTokFacebookThreadsInstagramLinkedInMastodonBluesky.


Hosted on Acast. See acast.com/privacy for more information.





Download audio: https://sphinx.acast.com/p/open/s/69c1476c007cdcf83fc0964b/e/6a4277403fa89e33389b083d/media.mp3
Read the whole story
alvinashcraft
57 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

e249 – Exploring the Balance Between AI Assistance and Human Expertise in Modern Presentation Design

1 Share
Show Notes – Episode #249 In this podcast episode, Troy, Nolan, and Sandy explore how AI is reshaping presentation design today. The conversation revolves around the two key spaces where AI operates: thinking (e.g. outlining, structuring) and design (e.g. visuals, layouts). While AI enhances efficiency, they also agree AI is not set [...]



Download audio: https://traffic.libsyn.com/thepresentationpodcast/TPP_e249.mp3
Read the whole story
alvinashcraft
57 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Rebuilding Observability for the Agentic AI Era with Suman Karumuri

1 Share

Suman Karumuri has spent 17+ years building observability systems at Amazon, Twitter, Pinterest, Slack, and Airbnb. He was tech lead for Zipkin at Twitter, co-authored the OpenTracing specification that fed into OpenTelemetry, and has now replaced Elasticsearch twice at high-traffic platforms. In this episode of the Smooth Scaling Podcast, Suman walks host Jose Quaresma through KalDB, the open-source, cloud-native log search engine he is building into a product, which runs at petabyte scale at Slack and Airbnb. They get into why he keeps rewriting Elasticsearch instead of tuning it, how separating compute from storage on S3 changes what a log system can do, and the recovery-task trick that keeps fresh logs visible when volume spikes 10x. The back half turns to agentic AI: why agents querying logs in unpredictable bursts break traditional log stacks, why you can't sample data anymore, and what engineering leaders should measure before the bill explodes. A concrete, in-the-weeds look at running log search when the primary user is no longer human.

Episode page

---

  • (00:00) - Intro
  • (01:04) - The origin story of KalDB
  • (05:45) - Why keep the Elasticsearch API
  • (07:09) - Separating compute from storage
  • (11:07) - Solving the 12-hour log lag
  • (14:02) - The journey of a single log message
  • (15:56) - What makes KalDB unique
  • (18:17) - Why not just use ClickHouse?
  • (22:12) - The polystore: search and analytics together
  • (23:38) - Native support for traces
  • (24:27) - How agents change observability
  • (31:24) - Chat as the UI, and what breaks first
  • (35:11) - What engineering leaders should do now
  • (39:54) - Build for a burning problem
  • (41:15) - Rapid fire: Acquired, and "scalability is..."

Suman Karumuri is the founder of KalDB, the open-source cloud-native log search engine he is now building into a product. KalDB runs at petabyte scale at Slack, Salesforce, and Airbnb. He spent 17+ years building observability systems at Amazon, Twitter, Pinterest, Slack, and Airbnb, was tech lead for Zipkin at Twitter, and co-authored the OpenTracing specification under the CNCF, which became the foundation of OpenTelemetry. He is based in San Francisco.

Suman has replaced Elasticsearch twice at high-traffic platforms. And with the rise of Agentic AI querying log systems in non-deterministic bursts, this places a whole new kind of stress on those systems to perform at high scale.


Suman Karumuri: https://www.linkedin.com/in/mansu/
Host José Quaresma: https://www.linkedin.com/in/jose-quaresma/ 

This podcast is produced and researched by Perseu Mandillo, and brought to you by Queue-it, your virtual waiting room partner. 

© Queue-it, 2026





Download audio: https://media.transistor.fm/5e82adac/c3286ab8.mp3
Read the whole story
alvinashcraft
57 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Why keeping Octopus up to date matters

1 Share

Octopus Deploy is purpose-built for deployment orchestration: tenants, runbooks, environments, lifecycle gates, and variable scoping, and is designed to work with whatever CI you already have. It’s infrastructure-agnostic by design, built for enterprise environments where teams run multiple clouds, target types, and toolchains at the same time.

Octopus comes in two flavours: Octopus Cloud, where we host and manage everything for you, or Octopus Server, where you install and run it on your own infrastructure.

Running an outdated Octopus Server is a quiet risk. This post covers why staying current matters, and why Octopus Cloud is worth considering if you’d rather focus on shipping software than maintaining the tool that ships it.

Below, I cover what Octopus updates actually contain, because security patches, bug fixes and more, matter just as much as new features.

Performance improvements

Performance is key not only for our customers but also for us. Every time we bake a new build internally, we test it to ensure it’s not worse than the previous version. We run tests against our software, and our staff get to try it out first before it propagates upwards.

You might be asking yourself, “What does this look like?” Bob Walker, Field CTO at Octopus, covers this in a great talk, available on YouTube. The talk covers how we ship changes, who gets to test them, and when these changes land for our self-hosted customers.

If you don’t already know, Octopus Cloud is one quarter ahead of Octopus Server.

So what does it look like? If the build is happy against automated tests:

  • Staff - We dog food our own app, our main deploy instance is the first one that’s updated
  • Canary Customers (+3 days) - We deploy to a random subset of Octopus Cloud customers, about 5% of active instances, which is randomized each time
  • Stable (+2 days) - We then deliver to the majority of our Cloud customers’ instances
  • Laggards - By this point, the release has already been running in production across thousands of instances, and we update the remaining Octopus Cloud instances
  • Octopus Server - Eventually, self-hosted Octopus customers will be able to download the latest version of our software

Should you want to learn more about performance for your self-hosted instance of Octopus Server, be sure to check out the documentation on performance. We handle performance for you when you’re on Octopus Cloud.

Improved compatibility & integrations

We’re always ensuring Octopus remains compatible with the most popular software tools and integrations. We have documentation on compatibility that goes into detail, as well as our integrations page on our website.

By staying up to date, you ensure you are ready for whatever the world throws at you and can adopt and implement new integrations as they become available.

Bug fixes

No one likes bugs; these can be nuanced and overlooked. You can view our release notes on our website, and you can also track which version you are on and which target version you plan to upgrade to using the compare versions option.

We present information clearly about breaking changes, bugs, and more.

Quality of life tweaks

We believe in listening to our customers’ feedback; it’s quite important to us and one of our core values for every Octonaut at Octopus.

Our customers help us sharpen our product even further, and we often revisit features, integrations, and more to refine them and make their lives easier.

You can learn more about Octopus’s core values in our handbook.

Security patches for CVEs

Everyone knows that a core part of keeping your software up to date is addressing security issues, and we publish this information in various places:

We also have a Security Disclosure Policy.

Compliance

Building on security patching, you have to ask yourself: how do you remain compliant if you don’t update your software regularly?

It’s important that you understand and upgrade your software regularly; this isn’t just an Octopus need, it’s for all software. By staying up to date, you ensure your business remains compliant and that audit checks pass with flying colors.

Enhancements to existing features

Just because we’ve shipped a feature doesn’t mean it’s done and forgotten; we’re always listening and looking for ways to improve what we offer.

You’ll always gain by updating Octopus software, and more often than not, you’ll learn about these in our blog section on our website. You can also subscribe, so you’re always up to date with any new blogs that are published.

A great example of this is Platform Hub, where we are releasing this functionality to our customers. You might be asking what Platform Hub is? Check that out in this blog post. We also have a feature page, should you be interested.

New features

We love building features that make developers’ lives easier.

You can see what we’re up to by visiting our public roadmap, leave us a signal on what’s important to you by voting, and you can also submit ideas directly to our product and engineering teams for consideration.

Staying within vendor support

Every Octopus software release receives six months of critical patches.

You can learn more about this on our blog post, where we discuss it, and in our documentation, which covers it for self-hosted Octopus customers.

Should you ever need to contact the Octopus Deploy Support Team, the team will be happy to help.

Deprecations

Occasionally, Octopus will deprecate features that will no longer be supported. These features are eventually removed.

Staying up to date means you’re protected against known vulnerabilities as soon as fixes are available, and you’re not carrying risks that have already been solved.

You can learn more about this in our docs.

Conclusion

The longer you leave it (not updating regularly), the more risk you carry, the more it costs to resolve when something breaks, and the longer it takes to get back on track. Staying current keeps your attack surface small.

If you prefer that Octopus handle upgrading Octopus for you, then I’d recommend Octopus Cloud. Octopus Cloud reliably hosts thousands of Octopus Deploy customers.

Octopus Cloud is the easiest way to run Octopus Deploy. It has the same software and functionality as Octopus Server, except we host it for you and we call it a Cloud instance. You don’t need to download, install, or manage it yourself. You can get started with a free account to try it out.

You can learn more about its architecture in this blog post.

Happy deployments!

Read the whole story
alvinashcraft
57 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories