Microsoft Word! Fuck you and the horse you rode into town on!
A while back, I had to code some custom plug-ins for our software product.
(It's extensible with User Apps which can be written in a variety of languages, but it's easiest to use Visual Studio and C# because it directly works with the API.)
This code had to do some Hard Stuff, involving Deep Magic.
Sometimes, one of the Hard Things is not the actual User Code, it's how to implement it properly as a plug-in for the main product.
(You are building DLLs, which need to both implement specific public interfaces which the main product can call into in order to use the plug-in, and also reference the main product API DLLs to be able to Do Stuff. )
I commented the code well, but I also wrote a Word doc describing how to set up the VS project correctly to integrate with our product, including screen-shots and code snippets.
I came to re-use some of those code snippets today, and copy-pasted them back into the new project.
A mess of squiggly red underlines.
"Are you perhaps missing a reference ( dumb_ass) ?" it helpfully asks.
Why, no! I am not. Fuck Off!
WTF?
Turns out Word has mangled the CaSe of everything in the code snippets when I wrote it up.
When I pasted the code snippets into the Word doc, Word decided that the CaSe needed 'fixing', and I never noticed at the time.
Cue half an hour of cursing and fixing it all back up.
I mean, it was everywhere.
From all the "using ThisThing" lines, through to all the class names.
And this ran very deep.
IDatabaseFactory, IDatabase, IWell, ICurveSet.
These things are referenced everywhere, and FuCkEd Up Case is a total PITA.