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.

C with C++ keywords
Solved with a simple parser/variable renamer.
abusing SEPPLES
Good job wasting your time. I hope you enjoy maintaining it, oh wait, you said you're going to rewrite it in straight C, which brings us to the first point.
Sexp-based languages
Most of the code I write is in CL, I have no problem with this, but I do think it's overkill to invoke Greenspun's rule that much. Using a real Lisp will give you much better performance, not to mention that you'll be able to take advantage of existing libraries and the excellent macro support and other language features which you'd have to write from scratch.