yes thanks a lot !
On Nov 15, 3:24 pm, Tim Barcz <[email protected]> wrote:
> So are you up and running? Can I consider this one closed?
>
>
>
> On Sun, Nov 15, 2009 at 1:50 AM, tom308 <[email protected]> wrote:
>
> > Tim
> > i can see that you feel a lot about laziness, and i am with you.
> > people should do what they need and not look for shortcuts, this is
> > the best way.
>
> > As a developer of an infrastructure layer, Post Sharp gives me the
> > ability to give better functionality, and in a very easy way for the
> > user.
> > It was totally my fault that led to my problem, and i have no regret
> > using it.
> > Tom
>
> > On Nov 12, 10:56 pm, bill richards <[email protected]>
> > wrote:
> > > Just an observation ....
>
> > > Tom, and herein lies the beauty of proper testing.
>
> > > The thing is though, I believe that if the code had been developed
> > > using a TDD approach, I am pretty certain that you would never have
> > > introduced such a bug. I think that this is a very good example of how
> > > 1) retro fitted "unit" tests can and do have at least some value, but
> > > more importantly how 2) developing WITHOUT tests can and usually does
> > > culminate in a flawed design at the functional level.
>
> > > And a little off topic ...
>
> > > Personally, I am a fan of any tool that can aid in making my job
> > > easier, lord knows we poor developers have to put up with a lot of
> > > rubbish from some people sometimes! However, is it really necessary to
> > > use PostSharp? What exactly is the point of these libraries
> > > (PostSharp)? Are they really anything more than a mechanism to enable
> > > me to write less code? I have seen examples of, heard about, and even
> > > had to deal with messes introduced through the use of PostSharp. I
> > > believe that use of these libraries encourage laziness in the
> > > coder ... INotifyPropertyChanged is a really simple interface to
> > > implement, why do people insist on creating a NotifyPropertyChanged
> > > aspect? all they have really achieved is creating dependencies upon
> > > libraries that only serve to stop me having to write as much code ...
> > > "Ah, but what if I have hundreds of properties on my class?" ... Then
> > > you have a design flaw right there in front of you! And the worst of
> > > the bunch is when it's used so that "you don't even have to write
> > > exception handlers"!!
>
> > > It's not a rant (or not meant to be), and I know it's not in the right
> > > group but it's something I had to say, sorry about that!
>
> --
> Tim Barcz
> Microsoft C# MVP
> Microsoft ASPInsiderhttp://timbarcz.devlicio.ushttp://www.twitter.com/timbarcz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Rhino.Mocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rhinomocks?hl=en
-~----------~----~----~----~------~----~------~--~---
