Notes

173 short notes on building software, going back to 2022. Most started life as an email to subscribers or a post on LinkedIn. The longer arguments end up in writing.

Notes

Most source-centric Dataverse pipelines I see are built by experienced architects from .NET or Java backgrounds.

Quick test: can you build a Power Automate Flow by writing its definition in your editor first?

Your source-centric Dataverse pipeline is environment-centric with extra steps.

I used to tell clients that migrating off their CRM was a 12-month project. That number is shrinking fast.

Win+R just got rebuilt with PowerToys DNA.

SAP just banned the AI that could help you leave.

The difference between a one-off AI session and a repeatable workflow is one file.

The best thing about AI as a pair programmer is that it never gets tired of me.

I never approve implementation until the plan that AI made survives interrogation.

Everyone is debating whether AI replaces developers.

AI does not need MCP to call an API.

The skill that gets automated first is the one that looks most like translation work.

Connectors were always training wheels.

Before you write a try...catch, answer three questions:

A conversation I have had dozens of times in code reviews:

I only code 20% now.

Stop naming your publisher after your company.

I used to see ChatGPT as my rubber ducky. 🦆

Finally, a built-in way to edit the command bar in Dynamics 365!

7 things I wished I knew early in my developer career.

AWS went down. And suddenly everyone became a cloud architect.

Ever seen an ALM consultant treat your PROD like a cow?

My Power Automate flows didn’t trigger after a restore.

.NET 10: ZIP it. Smarter.

.NET 10 finally fixes what Windows 10 broke 😅

This one Edge feature boosts my speed. And it’s off by default.

Just blogged 📢: The TypeScript Type Trap in Dynamics 365! 😎

I once ran a 12-person company.

Do you really need TypeScript in Dataverse?

The best code isn’t pretty. It’s invisible.

Earns Its Keep