
Technical blog by
Dom Reilly
Tech Lead and Senior Software Engineer specialising in .NET, Blazor, Optimizely, Azure, platform modernisation and technical leadership.
Senior Software Developer and Tech Lead working with .NET and Blazor. Sharing real-world problems, tech, and lessons learned - not always just development. Views expressed here are my own and do not represent my employer.
Recently published
Latest articles
The Migration Bugs That Actually Caught Us Out
The less obvious issues we hit migrating Optimizely CMS 11 to CMS 12 and .NET 8, including routing changes, JSON model binding, package dependency issues, Optimizely Forms email failures, and CMS authorization.
Read moreI Put Claude in Charge of GitHub Copilot During an Optimizely Upgrade
How we used Claude to plan and review an Optimizely CMS 11 to CMS 12 migration while GitHub Copilot handled the code changes, including the PowerShell driven workflow, migration safeguards, and the point where Claude...
Read moreThe Under-Documented Optimizely Caching API I Somehow Missed
I recently discovered some useful, but poorly documented, caching features in Optimizely CMS. Here’s how ReadThrough, ReadStrategy.Wait and master keys can prevent cache stampedes and invalidate custom cached data when...
Read moreReader favourites
Popular posts
The Under-Documented Optimizely Caching API I Somehow Missed
I recently discovered some useful, but poorly documented, caching features in Optimizely CMS. Here’s how ReadThrough, ReadStrategy.Wait and master keys can prevent cache stampedes and invalidate custom cached data when...
Read moreI Put Claude in Charge of GitHub Copilot During an Optimizely Upgrade
How we used Claude to plan and review an Optimizely CMS 11 to CMS 12 migration while GitHub Copilot handled the code changes, including the PowerShell driven workflow, migration safeguards, and the point where Claude...
Read moreThe Migration Bugs That Actually Caught Us Out
The less obvious issues we hit migrating Optimizely CMS 11 to CMS 12 and .NET 8, including routing changes, JSON model binding, package dependency issues, Optimizely Forms email failures, and CMS authorization.
Read moreConnect