Project Estimation: Help Me.

May 24th, 2007 § 1 comment § permalink

It seems like the estimates we make are always written in stone and no matter how many times we re-estimate, we never get it right. The plan team always want an earlier finish date and the developers always want a later finish date. How can you compromise?

1. How can you estimate the time it takes to analyze a project with unclear requirements? (We’ve tried to get better requirements, trust me…we have.)
2. How can you estimate for risks? We’ll mention the best case and worst case, but best case is usually the only date others see.
3. When creating an estimate everyone should be involved, right? How can you convince your business analyst to provide insight on their side of things?

CTRL + SHIFT + F, *uck Me.

May 16th, 2007 § 0 comments § permalink

We’ve been planning to use some type of data connection pooling for quite a while and decided to use the commons-dbcp from Apache.

In our applicationContext-jbdc.xml, we specify the url. I’m using Eclipse, so I formed a habit of doing a CTRL+SHIFFT+F to automatically format the XML for easy read before I deployed the project. BAD idea.


<property name=”url”>






<property name=”url”>



Ok, fine it was rejected. What was the error thrown?

org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC driver class ‘’

It took us FOREVER++ to find out where the hell this problem came up. BAH!

Exclusivity: Awesome Marketing Strategy.

May 12th, 2007 § 1 comment § permalink

Nowadays, if you’re in the “exclusive” group, you’re cool. It seems like there’s new marketing approach to the way products are being released (maybe its old and I just haven’t noticed). The Internet’s social websites today has allowed this strategy to blossom like crazy.

Step 1: Company has product X coming out. It’s announced at CES or a press event (Macworld or just a press release).
Step 2: Company releases “prototype” product X to limited users.
Step 3: Company says, “don’t show anyone.”
Step 4: Users let others know they have it. While using it, others ask about it and let others know.

Next thing you know, the product that was released to a limited number of people who aren’t supposed to tell anyone…is now known by the world through blogs, YouTube, etc.

What the world has become today…it’s awesome!

Oh yeah, by the way: I was at Flying Saucer for lunch today and Vikram saw some guy with the iPhone. I didn’t believe him, but he DID have it! It’s a SICK phone product. He happens to be a Cingular representative, therefore beta-testing the iPhone. He suggested us to wait until next year to get it. That’s when the iPhone will be on the 3G, instead of the slower 2G. Anyone hear anything about this?

***If he really is a beta tester and finds a HUGE bug, what will Apple do? I highly doubt its beta testing…it’s Exclusivity!

Just Getting the Job Done.

May 9th, 2007 § 1 comment § permalink

Seriously, why develop an application that just works. Ignoring best practices, design patterns, clean code, unit tests, etc. is a sin. Just because an application works, doesn’t mean it’s maintainable, easily extensible, and READABLE.

Clean up your code, help the next person who’s going to work on it.

"New" Elevator Technology?

May 1st, 2007 § 3 comments § permalink

For all those at 1111 Fannin, we hate this “New Elevator Technology.” It may just be that we’re running on old algorithm, slow CPU, or maybe its just the slow elevators themselves. Whatever the case, the elevators here suck. If a technology sucks it doesn’t matter if it’s new or old.

Also, it’s a choice of whether you’d rather wait in an elevator to get to your floor or wait outside until the algorithm determines the best action to take. Personally, both suck…maybe we’ve all grown to be impatient.

Where am I?

You are currently viewing the archives for May, 2007 at thomas nguyen.