Dependencies Suck.

March 16th, 2006 § 2 comments § permalink

Big, Old and Evolving Project = A LOT OF DEPENDENCIES.

Here’s what came up: We needed to insert dummy data to a database to test new Java code functionality, but the only way to insert it is to use the RPG interface (green screen) one at a time. It does a lot of business logic in the background, so we can’t just dump a bunch of data into the database.

Problem: there’s no function to do this. We HAVE to use the green screen. Imagine manually entering in 1000, better yet…20 individual forms (each form has about 15 fields) EVERY time you want to test your new Java code? THE SUCK.

Also, XMODS has no dependency when you buy engine upgrades. Stage 2 and Stage 2 – Upgrade is completely decoupled! AWESOME.

Coffee Break Anyone?

March 15th, 2006 § 0 comments § permalink

Free cup of *bucks coffee. What more can I say?

Pretty much any *bucks, you can’t miss them
Tomorrow, Wednesday, March 15, 2006
10:00 AM – 12:00 PM

A, B, or C?

March 14th, 2006 § 3 comments § permalink

Which one compiles?
Which has no exceptions?
Which works the right way?

A) isUniqueDealAs1.
B) isUniqueDealAs2.
C) Both.

(Java 1.4.2)

int _iNum;
int _iNum1;
int _iNum2;
String _strID;

public boolean isUniqueDealAs1 (FilterTestObject ftoR) {
   if (this._iNum == ftoR._iNum
         && this._iNum1 == ftoR._iNum1
         && this._iNum2 == ftoR._iNum2
         && this._strID.equals((String)ftoR._strID))
      return true;

   return false;

public boolean isUniqueDealAs2 (FilterTestObject ftoR) {
   if (this._iNum == ftoR._iNum
         && this._iNum1 == ftoR._iNum1
         && this._iNum2 == ftoR._iNum2
         && this._strID == ftoR._strID)
      return true;

   return false;

Oh the frustrations I had. 2 hours of debugging for one simple, simple, SIMPLE mistake.

Language/IDE Comparisons, Part 1.

March 12th, 2006 § 0 comments § permalink

Every once in a while, I’ll post up some new headaches, awesome-ness, or just differences that have come up for me using Java(1.4.2)/Eclipse (3.1.2) and C#(1.0)/Visual Studio 2003. Here are some to start:

IDE Features:
-Eclipse’s refactoring and perspectives are really helping me fly through the code and find what I need to find.
-Visual Studio 2003’s (VS2003) CTRL+Tab is much easier than Eclipse’s CTRL+F6 to move around open files.
-Eclipse’s support for JUnit testing, CTRL+X or CTRL+D, then T.
-VS2003’s support: a separate application, blech.

Parenthesis and curly braces:
-Eclipse auto closes it for you, VS doesn’t.
-VS2003 auto indents after you close it, Eclipse doesn’t.

Text navigation; CTRL (+ C) left and right
-Eclipse selects by word-“humps” i.e. thisClass has 2 humps, oneTwoThree has 3, etc.
-VS selects by word alone.

Langauage Features:
Verbatim string literals:
-They are a billion times prettier regular string literals. C# has them, Java doesn’t.

CSharpSqlStatement = @“SELECT *
FROM table1 t1
WHERE t1.column1 = ‘seacrhText’
ORDER BY t1.column1″;

javaSqlStatement = “SELECT * “
+ ” FROM table1 t1 “
+ ” WHERE t1.column1 = ‘seacrhText’ “
+ ” ORDER BY t1.column1″;

Try copy and pasting a statement from the SQL editor over to your code, then formatting it so Java can understand it. With C#, Copy and Paste inside parenthesis and let it know its a string literal with a ‘@‘.

Bundles of Fun.

March 3rd, 2006 § 0 comments § permalink

[1] Interviewing is Awesome.
Watching how people are on the other side of the interviewing table really opens your eyes. There are those who blow you away and others who you wish you could take to side and prepare them. Some people say “people skills” are something we are born with. I completely disagree. No matter what, it’s still a skill and everyone should work on it, but some just haven’t had the chance. To those who are quiet, un-engaging, and give two sentence answers in interviews, please go practice. To those who ramble on-and-on-and-on-and-on, do the same. Whether it’s to a friend, professor, mentor, or (I think is the best) your career counselor.

[2] Cougars Kill Owls.
The red sea. Coogs. UH. Whatever you want to call us, we beat Rice: 74-71. It was an awesome game. I had a roller coaster of emotions. Thanks to all those who came out to support: Sohel, Vikram, Long, Dustin, Luke, and the other ~7000 coogs! And yes, I still use my student ID to get in free. Better yet, we got 2 free hotdogs, 1 bag of chips, 3 shirts, and a FREE ride back to the car (thanks Long!).

[3] FINALLY, got project working (lessons learned).
After almost 2 weeks of struggling to get a stable copy of the application, it took only about 2 more to get it setup. First I tried WSAD, then I tried Eclipse…to my pleasing with success! Sometimes free is better than paying. Wait, I’m kidding myself. Free is always better.

Lesson 1: Position titles mean nothing if you don’t do what your position says.
Lesson 2: Being too busy to produce effective documentation makes things harder for the new guy. In this case, ME.
Lesson 3: If you don’t know what you’re talking about, shut your mouth.
Lesson 4: Micromanagement is good and bad depending on the circumstances. Long-term micromanagement is always bad.
Lesson 5: Understand the co-worker. Some come from completely different backgrounds.
Lesson 6: 13 really is a bad luck number.

[4] Articles and Blogs Galore.
a. Transformers are back!
b. Art History helps. I’d never care about this article without it.
c. Bird Flu? Psshh…we cook it until we KILL the flu.
d. If you have this poster, email me. I’ll buy it.

Where am I?

You are currently viewing the archives for March, 2006 at thomas nguyen.