in Search

Do you Twitter? Follow us @CodeBetter

Jeremy D. Miller -- The Shade Tree Developer

Under the hood and working with .Net, TDD, Software Design, and Agile Stuff

Published by

Comments

Brendan Tompkins said:

Welcome aboard Jeremy! We're all very glad you're here!

# July 18, 2005 8:50 AM

David said:

welcome, I look forward to your posts on SCRUM and agile processes

# July 18, 2005 9:46 AM

Welcome aboard from another part of the world. We have a place called Amerika over here but it does look a little different as most inhabitants emigrated to the US long time ago. And are now working in the shade of a tree.

# July 18, 2005 12:36 PM

rsakalley said:

Welcome Jeremy, would love to read about Scrum from you.

# July 18, 2005 1:54 PM

Carlton said:

I had to read that stupid "Fish" book, too. Who thinks up that crap?

There was also some other wierd book about pyramids or something - who knows what it was about anymore. When I told my boss I did not get much out of it, it was not long before I was eventually shown the door.

# July 19, 2005 8:59 AM

Jeremy D. Miller said:

Carlton, that doesn't sound like a place you'd miss much. We were *supposed* to read the Fish book. We were even supposed to carry around those silly fish stickers on our badges. I played hide and go seek quite successfully with the fellow who was in charge of insuring that everybody read the book.

# July 19, 2005 2:47 PM

shebert said:

Hi Jeremy,

Welcome, it's great to see you are blogging here! I've been following your blog for some time - now it's time to go update RssBandit.

-Steve

# July 20, 2005 9:04 AM

Raymond Lewallen said:

Code with lots of Debug.WriteLines probably have cyclomatic complexities into the 20s, and instead of recognizing the need to refactor so its easier to debug, they stink up the code.

# July 20, 2005 12:21 PM

Sahil Malik [MVP C#] said:

Jeremy Miller, the latest codebetter addition, blogged about an Amazing code smell - in which he basically...

# July 20, 2005 9:28 PM

Sahil Malik [MVP C#] said:

Jeremy Miller, the latest codebetter addition, blogged about an Amazing code smell - in which he basically...

# July 20, 2005 9:30 PM

Jeffrey Palermo said:

Great post! TDD is very straight-forward with class libraries, but I'm having a hard time right now because I'm writing web controls. I need to be able to test my web control in an HttpContext without running an entire web page.

# July 21, 2005 6:09 AM

Jeffrey Palermo said:

Awesome points. I see a lot of "unit" test code that is really just big, ugly automated tests. This test code touches all kinds of dependencies, and that's very hard to keep false negatives from happening. Keeping tests to one component at a time is much better. Atomic is the word. If a component needs outside data, mock it.

# July 21, 2005 6:12 AM

Jeremy D. Miller said:

Jeffrey, it might be an unpleasant experience, but I *know* that it is possible to create an HttpContext and make it current in a unit test. I've seen it done, I just didn't go look much at how they did it. You'll have to fire up Reflector to pull it off I'd imagine.

Let's talk about it at the Agile lunch today. I'm coming up on my first ASP.NET development in 2 years pretty soon.

# July 21, 2005 6:51 AM

Steve Hebert's Development Blog said:

I was reading Jeremy Miller's post on Code Smells
and another classic .Net code smell occurred to me.&nbsp;...

# July 21, 2005 7:42 AM

Steve Hebert's Development Blog said:

I was reading Jeremy Miller's post on Code Smells
and another classic .Net code smell occurred to me.&nbsp;...

# July 21, 2005 7:53 AM

Steve Hebert's Development Blog said:

I was reading Jeremy Miller's post on Code Smells
and another classic .Net code smell occurred to me.&nbsp;...

# July 21, 2005 8:10 AM

Jeremy D. Miller -- The Shade Tree Developer said:

Here's a&nbsp;handful of articles on designing with or for&nbsp;TDD I had&nbsp;originally posted on my...

# July 21, 2005 1:05 PM

Jeremy D. Miller -- The Shade Tree Developer said:

Here's a&nbsp;handful of articles on designing with or for&nbsp;TDD I had&nbsp;originally posted on my...

# July 21, 2005 1:05 PM

Jeremy D. Miller -- The Shade Tree Developer said:

Here's a&nbsp;handful of articles on designing with or for&nbsp;TDD I had&nbsp;originally posted on my...

# July 21, 2005 1:05 PM

Jeremy D. Miller -- The Shade Tree Developer said:

Here's a&nbsp;handful of articles on designing with or for&nbsp;TDD I had&nbsp;originally posted on my...

# July 21, 2005 1:05 PM

Jeremy D. Miller -- The Shade Tree Developer said:

Here's a&nbsp;handful of articles on designing with or for&nbsp;TDD I had&nbsp;originally posted on my...

# July 21, 2005 1:05 PM

Josh Pollard said:

# July 21, 2005 1:41 PM

James Shaw said:

"Sometimes it is absolutely necessary to maintain state between method calls or across threads and static *methods* are a logical choice"

Don't you mean static *members*? Static methods have nothing to do with state..

# July 21, 2005 2:37 PM

Scott Banwart's Blog said:

Jeremy D. Miller has posted a series of articles on things you should know before working with test-driven development.

# July 22, 2005 7:36 AM

Raymond Lewallen said:

Won't be my first tattoo, but I'm going to get one that says "Atomic Methods : Atomic Unit Tests"

# July 22, 2005 10:23 AM

Liang said:

That is so exciting. Really looking forward to it.

# July 22, 2005 1:27 PM

Jeffrey Palermo said:

These are some great tips. I use them at work all the time.

# July 25, 2005 6:42 PM

Christopher Steen - Learning .NET said:

Ajax.NET for Microsoft ASP.NET 2.0 (beta)
BackgroundWorker and Web Services
Data Source Controls...

# July 25, 2005 8:57 PM

Christopher Steen - Learning .NET said:

Ajax.NET for Microsoft ASP.NET 2.0 (beta)
BackgroundWorker and Web Services
Data Source Controls...

# July 25, 2005 9:00 PM

Christopher Steen - Learning .NET said:

Ajax.NET for Microsoft ASP.NET 2.0 (beta)
BackgroundWorker and Web Services
Data Source Controls...

# July 25, 2005 9:00 PM

rsakalley said:

While I am not a full fledged follower of Agile, (Emergent Design being one of the major reasons for that) especially for long term projects, I feel Emergent design is like letting a horse run within the circular wooden boundary. If you fail to define these, I think more things would break than make. So defining the boundaries is a must, and then let the developers loose, for the micro level emergent design, which actually comes out of TDD and Refactoring, nothing more nothing less. This may keep improving your macro level design, or may not.

# July 25, 2005 10:59 PM

Jeffrey Palermo said:

Emergent design. All the developers have to be very skilled for that to happen. So many programmers get things working and are content with crap that works. Agile assumes that the team consists of motivated, capable people. To do Agile development, you have to have the people first.

# July 26, 2005 5:59 AM

Jeremy D. Miller said:

Ranjan, I really only meant to avoid the extreme of "emergent" design. I would never support a BDUF approach. I prefer Jim Shore's description of "Continuous Design" (http://www.martinfowler.com/ieeeSoftware/continuousDesign.pdf). The key in my mind is to be thinking about the design and trying to improve every single day. Our development practice is still much closer to XP than something like RUP, and it works for us. I just think the zealot, purist approach to XP can be stupid. Design philosophy is a full range of approaches, not a binary switch, and there are plenty of folks out there doing XP and Agile well.

Regardless of approach, you're gonna want skilled developers that are working responsibly. NO process or design technique will ever change that fact. To Jeffrey's point, you really want the full team to be responsible for design or at least participate. If your developers need to be "coralled" you're already screwed out of the gate.

# July 26, 2005 6:58 AM

idior said:

the view how to tiger the _presenter.Close();

# July 27, 2005 6:12 AM

Brendan Tompkins said:

Outstanding!

# July 27, 2005 6:35 AM

Darrell said:

>> but I'm pretty sure you're not supposed to be sending raw exception messages to users. <<

Not to mention a security issue.

# July 27, 2005 11:28 AM

Jeffrey Palermo said:

Yeah, Jeremy. You are bigger than a lot of people. A corn-fed Texas boy!

# July 27, 2005 1:10 PM

Colin Kershaw said:

I think Bill had a great post that addresses the all too often overlooked focus on People:

http://www.williamcaputo.com/archives/000069.html

"In short," as he says, "... non-agile ... views process as having a larger impact on a project's success than its people...".

# July 27, 2005 3:04 PM

Harris said:

My thoughts...if you please...

# July 27, 2005 3:23 PM

Jeremy D. Miller said:

Thanks for the link Colin. Good to hear from you.

# July 28, 2005 3:10 PM

David Hayden said:

I second that. Excellent post, Jeremy.

Well written and a lot of great information. Welcome to CodeBetter!

# July 28, 2005 7:06 PM

Carlton Nettleton said:

Here's a question about namespaces in Dot.Net - everytime you make a new folder, you are essentially creting a new namespace. Just recently, I reorganized some DTO's (data transfer objects) into their own folder and needed to add that namespace to all my code (thank God for the compiler and my tests). Is this the type of thing you were referring to with this post? Or would the better course have been to keep the original namespace AND move into the new folder?

# July 29, 2005 1:48 PM