Sometimes, when I look at this article, I wonder if every programmer, software engineer, and developer would agree with this list. Personally, I do fully agree with the whole list. These are the type of habits and discipline that good and great programmers live by. Though, my question goes on whether or not the average (or median) programmer agrees with this list. Now, that's the question I have encountered in a lot of discussion with friends. Seven Habits of Highly Effective Programmers

Exchange Traded Notes. It has current exposure to the GSCI [GSP]. But Barclays is going to come out with another ETF later [GSG] without the debt note risk of the company. Barclays Files for Exchange Traded Note for Oil - How It Differs From The ETF - Seeking Alpha

The Art of SQL is a book that I've picked up recently. It seems to be a very good book on theoretical SQL. I'll write a review as soon as I'm finished.

The GSG is an ETF that I've been waiting for. The only other equity that mirrors against the Goldman Sachs Commodity Index (GSCI) is QRACX, which is closed to investments right now and requires a high minimum investment. Diversification into commodities will become a valuable tool because it has been proven to be correlated with inflation. ETFs » New iShares GSCI Commodity Trust - Key Points To Understand (GSG, DBC)

This is an interesting article on a topic that many people do not understand. It's worth a look. ETFs » Asset Allocation: Finding Your Risk Level

This is a very interesting article on how the backwards compatibility for the XBOX 360 is done. It makes me wonder if marketing was overzealous on this feature. Xbox Team : On Backwards Compatibility

Lately, I have been doing a lot of reading between Refactoring Databases : Evolutionary Database Design, Software Estimation: Demystifying the Black Art, and some of the new .NET books that were released in March 2006. Previously, I had the impression that experience and learning new technologies are the important qualities to get ahead. Though, I am beginning to get the impression that learning new APIs and libraries are not as important as being disciplined in writing quality code. In fact, the software engineering world is too mixed up in using the latest and greatest technology and not worrying about how to maintain and enhance current software. Picking up new technology has always been a habit for good developers, and, is therefore, the reason why I think building more quality and bug-free habits are better.

Software Estimation: Demystifying the Black Art sounds like it is going to be a good book. In my opinion, estimating is probably one of the toughest aspect of software development that you wish you never have to deal with. Hopefully, some good insight would come from this book, especially from the author of Code Complete. I will give an opinion of my findings as soon as I finish.

I never understood how the eBay.com Feedback system can work well with Half.com. Here's how I summarize the risks for selling and buying for each site

eBay.com Risks

• Seller: The risk that a buyer won't pay.
• Buyer: The risk that a seller won't ship the product or ship on time. The risk that the product is different than what was described.

Half.com Risks

• Seller: None. Payment already received and taken care by eBay/Half.com.
• Buyer: The risk that a seller won't ship the product or ship on time. The risk that the product is different than what was described.

In both cases, the Buyer should give feedback after receiving (or not receiving) the product. Though, the Seller has a risk that exists in eBay and not Half.com. In eBay, typically, the seller posts feedback as soon as payment has been received. In Half.com, it is puzzling how a Seller is able to rate the Buyer because the Seller has not gained any type of information about the Buyer. So, my thoughts are that in Half.com, the Buyer should be the post feedback first. Though, I'm not sure on what grounds a Seller should post, other than miscommunications.