Software management consultant and CTO, Headspring Systems
Browse by Tags
All Tags »
Coding Principles (
RSS)
-
|
I'll be attending the AltNetConf . Convenient for me that it's in Austin, TX. It's an open space conference, and I consider it the founding conference of a conversation that is "Alt.Net". I'll be proposing the topic: What are...
|
-
|
Technologies are coming and going faster than every before. In this environment, how can we provide companies with a good return for their software investment. Looking back, J2EE was all the rage. Software executives were banking on J2EE and making significant...
|
-
|
I have learned an important lesson from my combined experiences at all the places I've worked. That is: raw requirements cause waste. A term I've used (and have heard others use) is that requirements are either "baked" or "not baked"...
|
-
|
I subscribe to Martin's MVP pattern. If you are new to it, please have a read . It's a variation of Model-view-controller that puts more behavior in the controller and less in the view. I have tended to vary the amount of logic that belongs in...
|
-
|
Overview of Exceptions There are quite of a few things that are just laws of Object-Oriented development, and one of those is that exceptions should be avoided. If you can prevent an exception from being thrown, do it. In the world of managed runtimes...
|
-
|
Brian Button from the patterns and practices team gave a session bright and early Friday morning that was great. He covered how to write frameworks. What’s interesting is that he focused on writing frameworks as a non-technical problem since he’s seen...
|
-
|
If you remember the article in October that was on MSDN on Test-Driven Development, you remember the hub-bub that it caused because of the inaccuracies, and how it soon was pulled from the web. Microsoft has published new Guidelines for Test-Driven Development...
|
-
|
Not long ago, Jeremy Miller released version 1.0 his excellent dependency injection tool, StructureMap . I've ported it to .Net 2.0, and I've added generics to the bread and butter class, ObjectFactory. Download the . Net 2.0 release on sourceforge.net...
|
-
|
In this post, I'll talk about and demonstrate integration testing. If you are just starting out with integration testing, you want to test small before you test big. Full-system tests are good, but if they fail, they don't give much of a hint as to where...
|
-
|
I use NUnit for my automated tests. Because of that, all my tests are unit tests, right? WRONG! The name of the testing framework has no bearing on the type of test you have. NUnit is a framework for running automated tests. You _can_ write unit tests...
|
-
|
Reality In reality, developers don’t like to do much testing. Developers aren’t testers. We typically will write code while making certain assumptions about variables and, objectively knowing the expected behavior of the syntax, we might run it once and...
|
-
|
Writing software is too easy these days. Since it's so easy, there is a bunch of bad software out there. It's easy to write bad software. It's hard to write good software. Everyone needs software these days. From the home consumer to the large enterprise...
|
-
|
I've posted on a retrospective of my team's current release , and I've run a few code analysis numbers to get a baseline trend. I normally don't do code analysis since working code is our real goal, but here it is: I analyzed our latest component, which...
|
-
|
Here is the main reasoning for this: TDD states that a unit test is written before a unit of code. Each unit of code will have a unit test. When a unit of code needs to be refactored (changed in structure without affecting behavior), the unit test will...
|
-
|
If a class is well-designed, it will be easy to unit test. Good design speeds up unit testing, and TDD reveals bad design. In this way, TDD speeds up unit testing . For a very simple example, consider a controller class that takes a domain object and...
|
More Posts
Next page »