No Comments »

I was reading a blog post on a programming site about how to confuse coders that take over projects. One of the things they mentioned was to use hard to understand variable names. I decided to see how complicated I could make a simple program become by using stupid variable names. I decided I also wanted to cram it all into one file instead of separating it out into separate files for different classes. Here is my entire application:

using System;
using System.Windows.Forms;
namespace ___ {
static class _ { [STAThread] static void Main() { ____ _ = new ____(); } }
public class ____ { public ____() { __ _ = new __(); _._ = "(o_o)";
MessageBox.Show(_._); } }
public class __ { private string ___; public string _ {
get { return ___; } set { ___ = value; } } } }

This code will compile in stripped down WinForms application. Attached to this post is a zip file containing the entire source to the application. All that the application does is pop up a message box containing the string (o_o), then exits. Download the file ‘’ now!

You could, in theory, take this to the extreme, making your own classes for things like strings and functions like MessageBox to have nothing but underscores as object types and variable names, although those functions would contain the real C# function names. Anybody ever take this sort of stuff to the extreme?

Leave a Reply