Unfortunately, I doubt it will be. Programmers are some of the quirker people around, and when you slap a PhD on top of it, it becomes…crazy.
- The forementioned PHD likes to come up behind me and just pokes his face at my screen. “A-ha!” He would exclaim if I happen (heaven forbids) have a complier error. “Check the .h file!”, “Did you declare the function signature?” and so on and so forth.
Is it just me, or is it werid to loathe people peering over my shoulder uninvitied as I try to code? Or debug a problem? No big deal with pair programming (the other coder is invited, at any rate). But I just hate people who sneak up behind you and then ask, “Why aren’t your inheriting/using virtual functions/compositing/using pointers/allocate off the stack/using vector?”
- Supersitious DLL belief
“DLLs areeee evvilll!”
I got into an extended arugment over static builds and DLLs in Visual Studio. Needless to say, I understand what the PhD is saying about DLL hell. DLLs not found, wrong versions and so on. But what drives me into a frenzy is the unwillingness to tackle the problem. There are wills to solve the problems - manifest files and researching deployment strategies. But to him it is like some sort of arms war - I pull up some stuff to show it will work but he would retort “It didn’t work the other time with OpenCV!”
The one incident which almost had me vomitting blood is when I introduce to him Dependecies Walker, which can find out what dlls are missing, allowing me to identify them. He dropped this question, “Does Dependecies Walker needs a DLL?”
“Then what if the DLL it needs couldn’t be loaded?”
“It’s in the same folder as the .exe!”
“Yah, but what if it cannot be loaded! Or it depends on something else not found in the system”
Me: “Then the system is fucked and no way it would run our software”
- Meaningless jargon arguments
“I try not to use inheritance when possible” I said that. Bad big mistake.
“Ah-ha! Then you are using object-based, not object-oriented. Blah blah blah”
I need cotton wools.