My goal is to annoy other programmers

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.

>>9
Refactoring tools are beyond the realm of the typical idiot code-monkeys who fawn over Sepples like it's the fucking second coming of Jesus. I'd use Scheme where applicable; it's typically not installed and beyond the realm of familiarity of those calling the shots to what gets installed and used.

>>11
No:


$ cat main.cc
#include <iostream>
extern "C" {
#include "other.h"
};
int main(int argc, char **argv) {
    std::cout << other(1, 2, 3, 4) << std::endl;
    return 0;
}
$ cat other.h
int other(int this, int that, int new, int old);
$ cat other.c
int other(int this, int that, int new, int old) {
    return this + that + new + old;
}
$ gcc -Wall -c other.c
$ g++ -Wall -c main.cc
In file included from main.cc:4:0:
other.h:1:15: error: expected ‘,’ or ‘...’ before ‘this’
main.cc: In function ‘int main(int, char**)’:
main.cc:10:38: error: too many arguments to function ‘int other(int)’
other.h:1:5: note: declared here