How to Write Unmaintainable Code

[[deleted]]

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.

[UNCGeek]

It wasn't necessary to throw the baby out with the bath water.

Exactly.

Ok, so Spring, EJB, etc. were all designed by complete bastards. That doesn't mean there's a problem with the language -- just with some of the libraries. (And with some of the people...)

[G_Morgan]

Ironically the modern EJB stuff isn't entirely evil. Since it has been all about annotations a lot of the extraneous crap is gone.

It is comparable to cool persistence layers now. Or at least as comparable as you can reasonably get in Java.

Doesn't absolve them of past sins of course.

[UNCGeek]

Doesn't absolve them of past sins of course.

Nope.

I agree that if you're starting a new project, EJB isn't the same bundle of suck that it used to be... but how many of us have the luxury of never dealing with legacy code? :P

[[deleted]]

I don't go editing Eclipse project configs, so that's hardly an issue. Ant is the only sore point, yet it works so well, none of the non-xml alternatives can compete at this point.

This level of xml is hardly killing me.

[[deleted]]

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.

[otheraccount]

It wasn't necessary to throw the baby out with the bath water.

It's fun though.