http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/ micro-ISV Ramblings Fri, 12 Dec 2008 08:56:19 +0000 http://wordpress.com/ hourly 1 http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-5 Steep learning curves? « Dyonisius’s Weblog Thu, 02 Aug 2007 11:53:56 +0000 http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-5 [...] said in a previous post, commenting someone who’s love with NHibernate was over that it is benificial in later stages [...] [...] said in a previous post, commenting someone who’s love with NHibernate was over that it is benificial in later stages [...]

]]> http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-4 dyonisius Tue, 31 Jul 2007 17:24:36 +0000 http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-4 Once an app has been used for say a couple of months and meanwhile you're on your third or forth project since, you tend to forget the details of how, why and where you placed certain code if it is not layered and structured. In the past, I tried to enforce a certain structure on myself. But when I got to a deadline, I found myself to take shortcuts. Then when I came back to resolve a bug or something, I sometimes could not find where I'd put the code that is responsible for this or that functionality. Of course I'm not talking about a two page app here :D So I find with NHibernate, the fact you're forced to do something a certain way sometimes pays off. There are other things too, like database independancy. I myself once had a customer that wanted to change to MS SQL instead of MySQL. The sys admin left and the new one knew nothing about MySQL. I which I'd used an ORM then! they take care of the subtle differences between SQL dialects. Once an app has been used for say a couple of months and meanwhile you’re on your third or forth project since, you tend to forget the details of how, why and where you placed certain code if it is not layered and structured.
In the past, I tried to enforce a certain structure on myself. But when I got to a deadline, I found myself to take shortcuts.
Then when I came back to resolve a bug or something, I sometimes could not find where I’d put the code that is responsible for this or that functionality.
Of course I’m not talking about a two page app here
So I find with NHibernate, the fact you’re forced to do something a certain way sometimes pays off.
There are other things too, like database independancy. I myself once had a customer that wanted to change to MS SQL instead of MySQL. The sys admin left and the new one knew nothing about MySQL. I which I’d used an ORM then! they take care of the subtle differences between SQL dialects.

]]> http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-3 huenemeca Tue, 31 Jul 2007 15:14:13 +0000 http://dyonisius.wordpress.com/2007/07/31/some-disgrunt-over-nhibernate/#comment-3 Hey, I am curious as to what you see as the benefits once that app is live? Maybe it is too early to give up on NHibernate. Hey, I am curious as to what you see as the benefits once that app is live? Maybe it is too early to give up on NHibernate.

]]>