As February 2026 comes to a close, I wanted to provide a candid update on the progress of the SummitPoint Commander Tool and where things stand as we approach pilot readiness. Over the past several months, the focus has shifted from building core capabilities to validating them across real environments—both SharePoint Online and on-premises SharePoint. That validation work has required substantial refactoring, but it has also confirmed that Commander is behaving exactly as it

Happy New Year! Last month, I finally completed a major refactoring of the Commander Tool. The entire codebase is now in a second full pass of testing to ensure that all functionality, interface elements, and error-handling controls behave exactly as intended. While that milestone felt great to reach, I’ll be honest—it also came with a bit of burnout, compounded by the usual stresses that accompany the holiday season. Rather than pushing straight through, I decided to take a

It has been a while since my last update. Most of my time has been spent deep in the overhaul of the Commander Tool—an effort far bigger than I originally anticipated. While I’m not quite finished, I’m finally seeing light at the end of the tunnel, and I wanted to share the story behind what has changed, why it had to change, and where things are heading. The Backstory: When SharePoint Online Broke Everything In September 2025, I found myself wrestling with a big question: Ho

Lists are, hands down, one of the most powerful features of SharePoint. As both an administrator and a developer, I often prefer lists over libraries. From a technical perspective, lists and libraries are almost interchangeable—both store items, both support metadata, and both integrate with views and workflows. But if you’ve ever worked extensively with lists, you’ve probably encountered one of the biggest frustrations: field (column) creation and management. The Pain of Lis