<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener("load", function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <iframe src="http://www.blogger.com/navbar.g?targetBlogID=12803833&amp;blogName=thomasnguyen.com&amp;publishMode=PUBLISH_MODE_FTP&amp;navbarType=TAN&amp;layoutType=CLASSIC&amp;homepageUrl=http%3A%2F%2Fwww.thomasnguyen.com%2Fblog%2F&amp;searchRoot=http%3A%2F%2Fblogsearch.google.com%2F" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" height="30px" width="100%" id="navbar-iframe" title="Blogger Navigation and Search"></iframe> <div></div>
home blog contact

Project Estimation: Help Me.
Thursday, May 24, 2007
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?

Labels: , ,

1 comments
CTRL + SHIFT + F, *uck Me.
Wednesday, May 16, 2007
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.

Rejected!
<property name="url">
<value>
jdbc:as400://[dbUrl]/[library]
</value>
</property>


Accepted
<property name="url">
<value>jdbc:as400://[dbUrl]/[library]</value>
</property>


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 'com.ibm.as400.access.AS400JDBCDriver'


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

Labels: , , , ,

0 comments
Exclusivity: Awesome Marketing Strategy.
Friday, May 11, 2007
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!

Labels: , , , ,

1 comments
Just Getting the Job Done.
Tuesday, May 08, 2007
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.

Labels: ,

1 comments
"New" Elevator Technology?
Tuesday, May 01, 2007
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.

Labels: ,

3 comments





Recent Posts
Reading Material: Writing Secure Code.
No Right Click? Use Shift + F10.
Hurricane Ike Recovery.
CI in SD Conference.
Microsoft ArcReady Event.
University of Houston Alumni Organization.
Arrested Development - Great Show!
NYTimes.com - Double Click a Word, Try It.
Secure Vantage Technologies is Hiring.
SqlException: Invalid object name.

Archives
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
July 2008
August 2008
September 2008
October 2008

Blogger
copyright 2006-2008 | thomasnguyen.com

Google Reader flickr del.icio.us nike+