enterprise java
Wednesday, October 28th, 2009 04:01 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
afunaI am discovering, to my absolute horror that enterprise Java is a lot like myself: often has a point, but unable to get there without going on long rambling tangents; requires a lot of structure to hold itself together; loves, loves, loves to scatter and repeat itself everywhere.
I am reading tutorials on how to set up and use JPA. Sooooo many things that need to be set up before you can even test whether you can, say, connect to a database. And at that, all the articles make it a point to emphasize how wow, the new API makes life so much easier and better more convenient and faster than before (perhaps I shall one day see the difference, the way I did when I was being frustrated by maven's complexity, and then had to use ant briefly, which made me realize what all the fuss about maven was about)
I definitely cannot mistake what I am doing as anything other than work. Which is not a bad thing! I have plenty of toys to play with on my off time :)
Less frustrating, more flexible, more lightweight, more exciting, more practical, toys.
I am reading tutorials on how to set up and use JPA. Sooooo many things that need to be set up before you can even test whether you can, say, connect to a database. And at that, all the articles make it a point to emphasize how wow, the new API makes life so much easier and better more convenient and faster than before (perhaps I shall one day see the difference, the way I did when I was being frustrated by maven's complexity, and then had to use ant briefly, which made me realize what all the fuss about maven was about)
I definitely cannot mistake what I am doing as anything other than work. Which is not a bad thing! I have plenty of toys to play with on my off time :)
Less frustrating, more flexible, more lightweight, more exciting, more practical, toys.
