Taxes in the Future

For most of the United States, it was Tax day yesterday. Your federal, state, and local (if you have them) taxes were due unless you filed for an extension. And predictably, the news programs were filled with people complaining about our tax code.

I don’t mean they were complaining about the amount of taxes – though those people were out in force as well. I mean the people complaining about the “complexity of the tax code” itself.

Admittedly, it’s a bit… hefty. I wouldn’t want to have to wade through it on my own. And these collected quotes from lawmakers (interestingly, all complaining, all Republican) are pretty accurate about its length. The whole thing is over 24 megabytes in length – which sounds small in 2010, until you realize that a Gutenberg etext of War and Peace isn’t even four megabytes in length. At a rough guess, the US Tax code is about as long as all the books I read for my bachelor’s degree. I would hate having to read that mess.

But see, that’s the point. This is the future. I don’t have to read it.

My tax situation, like everything else in my life, has been complicated for years. But I’m willing to bet that I spent less time [1] doing my federal, state, and local taxes than my parents did on federal and state taxes when they were my age.

It took me three hours, a single file folder of needed paper receipts, and the documents I scanned into my PC. The local taxes (through the city’s website) took an additional hour; about a quarter of that time was because I didn’t read the directions carefully enough and made a mistake.

A simple tax system sounds great – but it ignores that our lives are complicated, messy things. All [2] those exceptions and changes and differences and just stuff that makes our tax code so big and unwieldy for people to read are there for a reason.

The thought of reading all that stuff – let alone understanding the legalese – is intimidating. Which is why I’ve used a tax-preparation program for the fourth year running. [3] Again, this is the future, dammit. All those complicated bits of the tax code? They’re just nested if-then-else statements. This is exactly the sort of thing that computers are made for. The existence of computers means that there is no need for most individuals to intuitively understand the tax code.

There are potential problems with this, which I’ll acknowledge briefly:

Popular posts:

  • Link Salad: References From The Digital Publishing Talk
  • A Quick Reminder About My "Artistic License" Policy (Or: I'm Not Talking About You)
  • It isn't how you screw up as a feminist. It's how you deal with screwing up.
  • Ignore stupid "scary" music. Go for some deeply creepy stuff this season.
  • The MarcoPoloization of Culture
  • What A Cover Letter Should Look Like When Submitting To A Magazine
  • Room Service - Published at the WiFiles

2 Comments

  1. April 16, 2010

    maybe we should write the tax code in Prolog or lojban.

  2. April 16, 2010

    Nah, I'd go for something easily cross-platform or cloud-based. Ruby? Python? Java? Something like that.

Comments are closed.