4 ms·
>excel is not usually treated as an engineering tool This is a good point. I've seen C# & Python devs who read the release notes and adopt new features of C#\
by clausok 8y ago
>excel is not usually treated as an engineering tool
This is a good point. I've seen C# & Python devs who read the release notes and adopt new features of C#\Python with alacrity while at the same time their Excel development work, which they spend considerable time on, evolves not at all. E.g., still using IF(ISERROR(...)) rather than IFERROR; VLOOKUP rather than INDEX(MATCH()); slow & brittle array functions rather than SUMIFS; employing many intermediate columns to clean out errors rather than using AGGREGATE(); doing things in VBA that they would never do in their primary programming language (v = Worksheets("pnl").Range("N22:N77").Value).
- intended 8y agoOoh aggregate, I didn’t know of that. Seems like overkill for my use cases. And as you know, there is no kill like overkill