Log in

No account? Create an account
entries friends calendar profile It's Me Previous Previous Next Next
The Autobiography of Russell
Life from a different perspective
Learning Java and its terms

I've signed up for a Beginning Java class at CSN. It was full but I emailed the instructor and he said to show up on Tuesday and we'll handle all the paperwork for me to attend over the attendance cap.

Hopefully this will help push me into learning another language that isn't complimentary to the ones I already know. Some projects at my job are adopting Java so it will also be useful in keeping up with their lingo. Do you have any idea how confusing people in the know can be to those not in the know? GlassFish, Hibernate, Metro, Maven, Spring, JPA, POJO? I had no clue what any of those were but they get thrown around with casual disregard for the transitive state of the company. I may be the only person in the entire company whose first language is PHP and not C#, Java, or Python. I finally got someone to sit down and explain what each is in terms that isn't entrenched to Java. I may still be slightly off, though, so don't take my word for it.

An automated framework to set up project layout, dependencies, and environment-specific information. This includes setup information for compiling the project (e.g. Ant or Make).
A web server in the same vein of Apache and IIS, except built in Java and internal to the application.
A library to access and provide web service calls specific to Java. This in the vein of SOAP, RPC, and such.
A DAO (Data Access Object) framework for accessing data from the database using object-oriented models.
Provides a bunch of modules to make various aspects of common project programming tasks easier, such as extending Hibernate to support Transactions, providing authentication/authorization, among other things.
JPA (Java Persistence API)
A method to persistent data access objects (DAOs) and an automated method to relate them to other DAOs (ala FROM table1 JOIN table2 USING).
POJO (Plain Old Java Object)
A Plain Old Java Object (POJO) is an object that has getters and setters yet no special logic. Basically a information storage definition class.

Now was that so hard?

3 comments or Leave a comment
(Deleted comment)
zimzat From: zimzat Date: August 31st, 2009 02:56 am (UTC) (Link)
It should be easy. Programming should never be hard.
raist_ From: raist_ Date: August 31st, 2009 03:07 am (UTC) (Link)
I learned Java as my first language in college (many colleges learn C++; ours learned Java), and I didn't have any idea what any of that stuff was.

However, I also don't actually working in the coding industry.

All in all, Java's very forgiving, and actually almost enjoyable in some ways. It's really just a happy version of C++.
zimzat From: zimzat Date: August 31st, 2009 03:20 am (UTC) (Link)
These are all terms being tossed around ("We decided to go with GlassFish over [the name of another Java Server]") at my job in the groups that are working on the new Java projects. It's the main things being exposed about the new projects. The rest of the developers are supposed to be keeping track of what's going on in these new groups since that's how it's supposed to be going for everyone over the long haul (or most everyone; it's possible my group may never move).

I really don't expect it to be hard to learn or program in. It's just a matter of getting started and changing the way I work. A structured environment that forces me to sit down and open a Java file is what I'm looking for in the Beginning Java class.
3 comments or Leave a comment