A very short rant (picture jumping-up-and-down tantrum) Throwing out all process and making the deadline for your new project, 30 days from now, does NOT make what you're doing “An agile process” it makes it “Hacking”. If you look at it as a first of many releases, then *maybe* you're heading there, but fricking-frack read a book about Agile and stop using it as a description for every train-wreck project out there. Agile has a HUGE amount of process, it just doesn't look ......
I'm sitting here, at my desk, at work, almost Midnight:30 on a Monday night. Why? I haven't done a major check in all day, and well, when I did, I broke the build. Currently I'm the only person working on the code base, so it might not be a HUGE deal if I just let it be broken for the night. However, I'm also in the process of trying to get agile practices implemented in our department. It all comes down to the two tongues that everyone has, the one in the shoe, and the one in the mouth. People have ......
The documentation on NMock is scanty at best, non existent at worst. Add into this mix that I self identify as a Mort. Someone who is generally more concerned about grabbing the data a customer wants and displaying it the way she wants it, so that I can pick up my pay check and go enjoy spending my money. Apparently, this combination has left me in the position of trying desperately to find example code to improve my oop skills while at the same time, educating me in exactly how weak my those skills ......
[Sent to Scott Adams] I have been a contract computer programmer for 14 years, and for about the last 5, have been telling people about what I call, "The Cult Of Wally" (Wally is my shepherd, I shall not want). An organization for the instruction of contract professionals and other people who are committed to a low stress life-style. I have absolutely no idea how to make this idea profitable enough that you would give your blessing to it. Being a complete ego-maniac however, I would love to get some ......
Something interesting with NMock. If you set an ExpectAndReturn block and then set a watch on that value, you could will end up with a NMock.VerifyException. Here's what's going on. When you set the ExpectAndReturn, like this one fooMock.ExpectAndReturn( “LoginEnabled“, true ); you are saying that you expect your mock to check the value of LoginEnabled one time. If you want to use that value twice it would look like this: fooMock.ExpectAndReturn( “LoginEnabled“, true ); fooMock.ExpectAndReturn( ......