ingenious code ::

I read today the excellent article Steve Joubert article about project management. I agree completely with the idea of involving all the practitioners in the development software with the client. However, this way of work has a disadvantage which is the that usually, some members of the development team are very technical people who are not savvy in the way you should approach project requirements the client. When dealing with a client, even after the project signed on, the client especially if he/she is a new client, is always checking his provider to verify that he actually made the right decision. What I believe that there should be a representation from each of parts of the development team, but you have to verify that you chose the right personnel to work with the client.

It’s been a while since I published something on my Blog. What can I say? it was a crazy month. I was working like crazy on our corporate website. We launched the beta version two weeks ago and got a lot of positive feedback, so I am excited of the new possibilities I could have with the new website as a marketing tool.
Anyhow, Yesterday I did something out of the ordinary and assisted one of clients to upgrade his server which included upgrading his SQL Server 2000 to 2005. The upgrade went smoothly on the SQL Server (Surprise!), but then it came the turn of the applications that were installed on the server. One in particular was driving us crazy as the sa password of the SQL Server was hard coded into it (!). The only problem was, the client didn’t know the sa password, it wasn’t written down and of course the password is encrypted in the syslogins table (master database)..
After trying in my bag of tricks without any results, I consulted my friends at SQLServerCentral.com and they recommended a utility called SQL Crack from NGS Software.
This utility is used for checking the security of the passwords on your SQL Server. Well, my assumption was that who ever set the password didn’t put a strong password and I was right. It took the software 20 seconds to crack the sa password and save the day. Needless to say that we changed all the other passwords it could crack to a strong password

Well, it took some time but in the end I made my self seat down and start blogging. Why? well… in the last couple of years I am really enjoying reading some blogs in the vast space of the internet. I found that I am getting a lot from reading other people recommendations, thoughts etc.
So, I decided to contribute my own thoughts and wisdom (?) with others. Also, as I opened my company two months ago, I would like to use this blog to share my experiences on building a brand new ISV. My company’s name is CSW Solutions and we are located in downtown Chicago. Currently, we are working in multiple are trying to find a niche that will allow us to grow.
So I would like to thank first of all my blog comrades that inspired me and drove me to start this endouver. (You will find some of them on the right side of the screen!)