I have tons I need to blog about but no time to do it, as once again I am up to my head in projects. So this entry is going to be to vent....

One of my current clients is requiring me to use a product called LLBLGen Pro (see it at http://www.llblgen.com). I am certain it's a powerful product, and while it generates enough code to make a COBOL program to look efficient, it seems to perform OK, although my gut tells me this thing would be a pig in a high-demand environment. But here's my gripe -- the documentation is horrendous. I have spent at least 50 hours trying to get this thing to generate code effectively as well as consistantly. And even then, I don't understand a tenth of what's generated. I understand enough to make minor changes, and after a lot of wrestling, I can finally get it to generate code. OK, 50 hours may not seem like a lot to learn a new paradigm which might reap a lot of benefits later, but let me tell you what that 50 hours (billable to my client, I might add, since I begged them after 10 hours to scrap it) bought you. I managed to add 2 fields to a table, and add two tables. The two new table still don't work right.

Let's put that into perspective. First, I code lightning fast. Not spaghetti code mind you, but robust code which typically is right the first time. In that 50 hours, I could have re-written a good chunk of the app, and believe me, it needs it. Fortunately, I did my consultant's duty to bring that point up. It would have taken me three hours tops to make the changes which we are looking at 50 hours and still not working. 

Second, the code is difficult to read at best. The project has fallen behind because of the insistance we use this tool, so they brought on two other developers. Guess what, they are having the same problems. They have spent two solid days now, and not one line of code written. Using standard objects, any developer with experience in .Net can peruse the object model quickly and begin coding. Not with this tool!

You can't compare CodeSmith, which I have praised before, with LLBLGen. LLBLGen is far more sophisticated, unfortunately to the point of being unusable. I know there are a few people who swear by it, and that's great, but I get paid to come in and make a difference fast, and LLBLGen has proven to be more an expensive hindrance than a solution.

OK, that's the end of the vent. I have been deploying some web services for another client, and once we have everything debugged, I have a ton of tips related to web services and deployment which I promise will save a ton of hours to other developers entering into this domain. Until then!