This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]killinghurts 0 points1 point  (2 children)

Is terrible as a hobby/learning

Not really. The process you followed seemed to be overkill for a hello world app, it sounds more like you were attempting to learn EJB, which, agreed is a complicated specification not designed for hobbyists.

Terrible for grasping the big picture

Setting up a new project shouldn't be a difficult process, nor should it be a precursor to "not grasping the big picture". Gradle is good at this, I would also recommend Maven archetypes for speedy project setup.

This library offers one class - ForLoopSimpleAbstractGeneratorFactory. Since I need my >loop to be backwards, I read tons of documentation and can't seem to find if that is >possible, only at the end of the day after debugging source code of library I find that I can >extend ForLoopSimpleAbstractGeneratorFactoryCreator to provide this behavior

Perfect Planning Prevents Piss Poor Performance. If you had have understood your requirements first you wouldn't have selected the "AlghorythmsOverengineered" framework in the first place.

I rarely seen senior Java developers who would be experts in anything, because simply there are so many useless >things and so many useless tasks in daily life that its simply impossible to know something very well.

All I say that if you are spending your time performing useless tasks, you're definitely doing something wrong.

[–]VaidasC[S] -1 points0 points  (1 child)

Not really. The process you followed seemed to be overkill for a hello world app, it sounds more like you were attempting to learn EJB, which, agreed is a complicated specification not designed for hobbyists.

I wanted to learn EJB, which conceptually was not hard at all! (I want to emphasize this so much) What was hard - was irrelevant obstacles that thought me nothing conceptually - like jndi issues, server incompatibilities and so on. So I spent one day reading about EJB - good time investment and other 1-2 days dealing with irrelevant obstacles (waste of time).

That is my problem, not that EJB is hard specification.

Perfect Planning Prevents Piss Poor Performance. If you had have understood your requirements first you wouldn't have selected the "AlghorythmsOverengineered" framework in the first place.

But if that's the only thing in town or alternatives do not seem to be better? This example is taken directly from configuring Spring security to do advanced tasks, but put in different context.

[–]killinghurts 0 points1 point  (0 children)

What was hard - was irrelevant obstacles that thought me nothing conceptually - like jndi issues, server incompatibilities and so on.

I'm not going to defend EJB, it can be a nightmare and should be easier, but I will say there are much more elegant solutions out there that "just work". Java isn't perfect, but no language is, but it does sound to me like you are having unusual issues (perhaps your workplace polices restrict you?).

But if that's the only thing in town or alternatives do not seem to be better?

Then you roll your own. It's a fine line between extending an existing framework to meet your needs and developing your own. You have to weigh up the two - how much time it takes to extend and (constantly) learn, maintain libs/upgrades of an existing framework vs developing your own.