> "Bring the VBE into this century!" This actually gave me goosebumps... Are there many modern use-cases for Visual Basic? All I can think of is horrible scripting code for Excel, Word and AutoCAD
Anyone that inherits any sort of legacy MS Office workflow almost always needs to interact with VBA. Access, Excel, and Word workflows use it excessively as it's the only language you can use for manipulating things "inside" the file. Sure, you can use something like DAO/ADO/ODBC to perform CRUD type operations on the file from some other program. But if you want to, say, attach some code to an event in an Access form, you're stuck with VBA. So a tool like Rubberduck is useful to people developing for legacy Office related code, especially since VBE by default isn't super great. Access seems to be dying out but Excel is still flourishing.