When you're just writing a list of values, then Excel is just fine. The problem comes when they start trying to use Excel like a database (e.g. querying, creating data entry forms, performing integrity checks, etc.)
@IvenBach no, but if an interface uses them I'd typically declare them in the same module as the interface. otherwise, they could be defined in your Constants standard module
I don't remember -- maybe @MathieuGuindon remembers --- Joel Spolsky made a video explaining how people fall in the same trap over and over when the users make feature requests.
That's exactly how it should be --- purpose-built rather than hijacking some spreadsheet.
To clarify, not just any kind of feature requests --- they usually frame their feature requests in way like "hey, can you make it work like Excel does?"
when RD hijacks the code panes (yes, that's AvalonMentions++;), I'll be happy to configure an actual theme, ...with better colors than the 1992 craptastic default palette
There was that issue someone submitted showing a dark theme. Granted the link to where the got it from was crawling with trojan's and other nasty STDs.
I guess DTD (Digitially Transmitted Disease) would be more pedantic.
well the solution they got was to literally rewrite VBA7.DLL (IIRC), tweaking the bits that define the color palette. no way Rubberduck was going to do that
> Comic Sans was originally designed to be used in the talk bubbles of a program called Microsoft Bob.
OMG
> The font wasn’t completed in time to actually make it into the program, but it lived on to eventually ship with Windows 95; and that’s when the font really got ugly.
> This is a monumental moment in history – right up there with the invention of printing – for common people to suddenly have the power to typeset and print documents.