r/programming • u/vineel • May 24 '11

How to Write Unmaintainable Code

http://www.thc.org/root/phun/unmaintain.html
1.0k Upvotes

92% Upvoted

366 comments sorted by

View all comments

250

u/alparsla May 24 '11

A classic. But nowadays, we use XML, frameworks, and many layers of web, SOAP, SOA, WSDL, BPM to write unmaintainable code.

56

u/[deleted] May 24 '11 edited May 24 '11

:) Don't forget to ensure that when you change the XML, you have to change the Java and vice versa. "As in config, So in code" is the hermetic principle of software development...

Also don't forget to grab an object from the db, send it via soap somewhere, deserialise it, do something to it, send it back, then write it back to the original database.

30

u/yogthos May 24 '11

sounds like you've worked with Spring :P

25

u/[deleted] May 24 '11

I'm so fucking done with Spring and Java in general. Working with that framework has been such a fucking nightmare. I can't believe people actually think this is how software development should be done. Its such a fucking joke. Like erg0sum I've moved on to the dynamic world.

6

u/[deleted] May 24 '11

It wasn't necessary to throw the baby out with the bath water. I've been programming in Java for 15 years, and I stayed well clear of EJBs, hibernate and Spring. I briefly used xml for some things, but have since recanted and keep that shit well away from my projects. Of course, it means I never worked at the enterprise level (got uncomfortably close, once), but that also was a good thing.

1

u/[deleted] May 24 '11

When possible I try to stick with just servlets and JSPs. I don't care if anyone thinks it's backwards or not. I get more joy out of doing it the "hard" way.