Name: Anonymous 2010-06-13 16:34
I bet some of you do this, too.
In my C code, I use C++ keywords for my variable names whenever I can. I'll use variable names like "private" and "catch" in header files, so they can't be included in C++ code. I name my variables "old" and "new", or "this" and "that". I also deliberately skip casts in situations where they'd be perfectly ok in C but invalid in C++.
If I do have to use C++, I make sure to use every possible feature of the language. I strive to systematically piss off anyone who forces me to deal with C++, so that everyone else quits. Then, I will rewrite the entire system in straight C, cut the codebase to a quarter of the size, and make it ten times more readable.
For very large tasks, I will first design a sexp-based domain-specific language, and then proceed to write the entire project in that language. I will make sure that it is slightly different from every existing Lisp implementation, because my boss might have read somewhere that Lisp was antiquated and inefficient.
I am the programmer that employers hate.
In my C code, I use C++ keywords for my variable names whenever I can. I'll use variable names like "private" and "catch" in header files, so they can't be included in C++ code. I name my variables "old" and "new", or "this" and "that". I also deliberately skip casts in situations where they'd be perfectly ok in C but invalid in C++.
If I do have to use C++, I make sure to use every possible feature of the language. I strive to systematically piss off anyone who forces me to deal with C++, so that everyone else quits. Then, I will rewrite the entire system in straight C, cut the codebase to a quarter of the size, and make it ten times more readable.
For very large tasks, I will first design a sexp-based domain-specific language, and then proceed to write the entire project in that language. I will make sure that it is slightly different from every existing Lisp implementation, because my boss might have read somewhere that Lisp was antiquated and inefficient.
I am the programmer that employers hate.