JLinX – Blog

• Patterns for Generation, Handling and Management of Errors
• More Patterns for the Generation, Handling and Management of Errors

http://www.se.eecs.uni-kassel.de/

Linda Rising – Patterns Almanac 2000

On October 4, 2001, Mike Hill (then of Object Mentor, now of Industrial Logic) visited NASA Langley Research Center in Hampton, Virginia and gave a test-first design talk at the Institute for Computer and Applied Sciences and Engineering (ICASE). Copies of his slides are available at icase.edu/series/MPP.

Mike spent the afternoon with Bil Kleb, Bill Wood, Karen Bibb, and Mike Park reasoning out how we might create a testing framework for Fortran 90 to use during FUN3D code development. By the end of the afternoon we had a working prototype based on the macro expansion techniques employed in Mike Hill‘s cpptestkit. We quickly found C-preprocessor macros to be too restrictive and rewrote the framework in Ruby.

More information: http://funit.rubyforge.org/

 

dnrTv is a fusion of a training video and an interview show. Training videos are typically sterile and one-way. Let’s face it, you can only take so much. But you need to see the code! In this format, you get the spontaneity of an interview talk show, and the detail of a webcast or training video.

Carl Franklin is the host of the wildly popular mp3 talk show .NET Rocks!, which he started recording in August, 2002. dnrTV launched on January 12th, 2006, the same week as .NET Rocks! show number 159!

We see dnrTV as a natural adjunct to .NET Rocks!, allowing more technical topics to be explored in detail. As always, Carl keeps the atmosphere light and conversational, which makes for a nice way to spend your lunch hour!

Have a look at dnrTV.com…

• Model View Presenter mutated: Observable View
• Considering a View’s Get/Set Roles with MVP
• Jean Paul Boodhoo on Model/View/Presenter (vidoe at dnrTV)

Have a look at devlico.us

In this article, Scott Meyers shares his picks for the five most important books in the history of C++, along with why he chose them…

article at artima.com

• The name of the method should describe what the method actually does.
• A method should do one and only one thing.
• A method should either DO something or RETURN something.  If it returns something, you should be able to call the method over and over with no negative consequences.
• The method should be viewable without scrolling.  Fewer than 10 lines of code is desirable (my pain point).
• The method should take few arguments.  If the method needs more, refactor to require and object that contains all the information required (parameter object).
• The method depends only on method parameters or members passed into the class constructor.
• A method should only have one indented code block – don’t nest code blocks.  Extract method first.
• Don’t try/catch in a method unless you can handle the exception or add value.  Let the exception bubble up to a point where you can actually do something about the exception.

(Quelle: How to design a single method – Jeffrey Palermo)

• Jeremy D. Miller
• Jeffrey Palermo
• Jean-Paul S. Boodhoo
• http://www.jpboodhoo.com/blog/

• Test Driven Development with ASP.Net and the Model View Presenter Pattern
• TDD Design Starter Kit – Dependency Inversion Principle
• Mock Objects and Stubs: The Bottle Brush of TDD
• What’s so great about Inversion of Control?
• The Dependency Injection Pattern – What is it and why do I care?