By Hiran de Silva Randy Austin recently sparked a lively discussion with his thoughtful comparison of VBA and Office Scripts. But as important as syntax and capability...
Author - Hiran de Silva
Excel Ignorance: The Price You Didn’t Budget For – Part 2: The Solution They Said Couldn’t Exist
By Hiran de Silva In Part 1, we explored a provocative challenge: a seemingly simple spreadsheet operation that worked perfectly for one call handler—but fell apart at...
By Hiran de Silva In this article, I want to show how the incorrect use of Excel—or more accurately, a lack of proper understanding of its capabilities—is costing...
From Digital Duct Tape to Digital Fortress: Solving the Excel Problem with a Hub-and-Spoke Model
By Hiran de Silva This is a follow up to the earlier article on ‘Excel Hell’. In our previous discussion, we explored the hidden dangers of running an...
By Hiran de Silva There’s a certain kind of performance art that takes place on late-night TV and LinkedIn feeds alike. You know the type: A slick-tongued grifter in a...
Thought Experiment: The Power Query Paradox — When the Solution Exists, But Only If It’s Trendy
By Hiran de Silva There’s a strange and revealing contradiction making the rounds on LinkedIn, courtesy of a post by Alfio Auteri. His post praises Power Query in...
By Hiran de Silva In the last 10, 15—let’s just round it up to 20—years, something rather curious has been unfolding in the world of Excel. Microsoft, in its boundless...
Refuting the “Rocket Science” Myth: Why Mark Proctor’s View on Excel Reconciliation Misses the Point
By Hiran de Silva Podcast narrated by Charlie. Mark Proctor is a respected voice in the Excel community, and in one of his videos, he walks through a method of...
By Hiran de Silva Over the last two decades, a quiet transformation has reshaped Excel—and not necessarily for the better. Microsoft, once the champion of end-user...
By Hiran de Silva Jordan Goldmeier once asserted there’s nothing you can do in Access that you can’t do better in Excel. It’s a bold claim—and a category error. It’s...

