Not exactly dev stuff, but LaTeX low-key makes me nervous.

In writing my thesis it seems that through some keyboard-fuckery I managed to slip in some weird unicode bullshit character somewhere, so that it doesn't compile. Alright, I just do \DeclareUnicodeCharacter{0301}{ASDF} so that it gets replaced by ASDF. Searching for ASDF in the output pdf file does not yield results, so I can't even find the location of the fuckery in the text. It seems that unicode character is somewhere in my .bib-file and I guess my citation style doesn't even render the part of the data that character is in after all. So the above hack works, but still there is some weird-ass character in my bibliography file that I can't find.

On another note: I get that modularity is cool and all, but who thought that it is a good idea to give people zero transparency over what macro stems from which included package? No namespaces etc. I end up including a whole lot of packages that are needed for exactly one macro. That bloats up the file and you have no way to trace back which macro came from which of the quazillion included packages.

...then again maybe I'm just a lazy piece of shit whose google searches end before success and all of the above has some easy fix.

u+200b.
Who made that shit? and whhhyyyyy?
I spent 20 minutes trying to figure out why the code file, a mac using co-worker sent me, does not compile.
Intlij did not help, np++ did not help, textmate did not help!

Only hex editing the file worked!

kill it with fire!