Here's 2 small debugging tips :
- understand the code you're trying to fix.
Debugging code written by somebody else sucks but it's very important to grok the code before debugging it. Only when you understand the problem you should attempt to fix it.

- be well rested and have a clear head.
This is very important. If you're tired you might spend a lot of time trying to fix something only to find out that it took you 5 min the second day when you were well rested.

There are some changes to the BusinessObjects implementation in DataBlock 1.4 .Now there will be 2 types of objects generated for each entity :
- the DataAccessObject : this resembles very much with the old BO objects. It's a typed DAL for a entity. The idea is to use this DAL from a high level "custom" BO.
- the new BusinessObject. This is a clean implementation with supports only the "basic" operation for a entity : Create, Delete, Update and Read. The underline implementation of this is the PersistentObject. This is also used to implement your custom business logic. Write the queries using QueryCriteria and pass them to the persistent object.
So those 2 methods...do we really need them both ? Yeap...choice is the name of the game here. Some people will like to use the built in BOs while others will prefer to use the DAL and build their own BOs.
This way everybody should be happy :)

You're bullshitting Google

It was planned for yesterday but i had to push it back due to some bugs. Hopefully not for long.

If you read fantasy then probably you heard of "Sword of Shadows" series by J.V.Jones. I can't confirm if the series is great of not because i have a habit of not reading series of books before the last volume is published. So wanting to read something by JV Jones, i have settled for "Book of Words".
It's a interesting read....more of a "light" fantasy but, nonetheless, interesting story and characters (although the characters were a bit "cliche"). The storyline itself could have been a little more "fleshed out", but in the end the books were worth reading.

Charles Petzold wrote a while back about why it's not worth it anymore to write tech books.As a avid reader i'd thought to write a few opinions for tech books writers :

- don't put meaningless crap in the books. No pictures of Visual Studio, setup images, incredibly large code pieces and other crap like this. A technical book should contain only meaningful content.

- write focused books. Between 2 books on the same subject i will always choose the short one. My time is limited and usually thick books are filled with crap (see previous point). Here's a example of bad writing. I've read 2 books from APress by Laurence Moroney : Foundations of WPF and Foundations of Atlas. The first chapter of both these books is pretty much the same and it presents a history of the graphic user interfaces. Well...personally...when i buy a book about WPF i expect to read about WPF. If i'm interested in history of GUI i'll look it up on wikipedia.

- have ""hardcore"" content. Tips and tricks books won't cut it. There's a wealth of free content on the web : articles, blogs, MSDN etc. Your book directly competes with free, easy accessible content.

- the dead tree version of the book MUST come with a ebook version. Reading the dead tree version is great but the sad reality is that we can't do that all the time. I do the bulk of my reading while riding the metro to/from work.

- sell a ebook version at a considerable lower price.

- you if jump in the bandwagon of books who cover API's make sure you really know your shit. Keeping the WPF example.....there are LOTS of WPF books on the market but only a couple of them are worth reading.

This is easily one of the best programming books i have ever read. Simply put it, it's about building software for the real world. About designing a system that works well in a real world and that can take a ""beating"" :D.
It has plenty of good advices on how to achieve that.

Recommended

Small update on DataBlock's next release:
- lots of changes and bug fixes to the Modeler. Finally it will have the option to load the table relations from a existing file.
- paging implementation for sql server. I will implement a paging solution which will work on all SqlServer versions (that means no ROW_NUMBER trick).
- additional library fixes.

The books is described as ""a collection of tips that show you what tools a successful team has to use, and how to use them well"". My problem, as a professional software developer, with the book is that it's kind of light on content for professionals. I mean....telling me that i need to use source control is useless. I already know this stuff.
So, in the end, i guess the usefulnesses of the books depends very much on the level of the reader.