<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>mentis vulgaris</title>
	<link>http://numainnovations.com/mentis-vulgaris</link>
	<description>Simple thoughts about software, business and one or two other things</description>
	<lastBuildDate>Fri, 03 Sep 2010 22:51:47 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Promises, Promises</title>
		<description><![CDATA[Promises are like babies: easy to make, hard to deliver. ~Anonymous
Every .NET interface, every COM interface, and every API is a promise.   A contract of sorts.   We all know that &#8212; it&#8217;s the point of an API.   But, have we really thought about what that implies (especially in the [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/promises-promises/</link>
			</item>
	<item>
		<title>Software Craftsmen, Laws and Principles, Oh My</title>
		<description><![CDATA[Many software developers have written about various Principles and Laws of software development.  We talk about things like SOLID, OCP, SRP, LSP, DRY, LoD, and whether these things help or hinder.  To outsiders it seems we spend a lot of time arguing the software equivalent of how many angels can dance on the [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/software-craftsmen-laws-and-principles-oh-my/</link>
			</item>
	<item>
		<title>Using Velocity Charts and Burn-Downs to Drive Development</title>
		<description><![CDATA[Imagine you’re the driver in a car cruising along the Seven Miles Bridge in the Florida Keys.  Sunny day.  Clear.   There are no other cars, and you’ve been given permission from the Florida Troopers to go as fast as you like – so you’re cooking along at 80-90 miles an hour.
Now [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/using-velocity-charts-and-burn-downs-to-drive-development/</link>
			</item>
	<item>
		<title>The Bottleneck</title>
		<description><![CDATA[Nearly 70% of all software projects are considered unsuccessful.  They are late, over budget and have fewer features than users wanted (and often ones they didn’t want – I’m looking at you, Clippy).   
I gotta ask, would this situation exist if we had perfect knowledge of the future?  
If we knew [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/the-bottleneck/</link>
			</item>
	<item>
		<title>Exceptions are Easy.  Except When They&#8217;re Not (Part 2)</title>
		<description><![CDATA[Nothing is said which has not been said before. ~ Terence (195/185 BC-159 BC) Playwright of the Roman Republic
In a previous post, I posed two questions to my readers (all √(-1) of them): whether a body of code was exception safe, and if there was anything I needed to change to insure the code was [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/exceptions-are-easy-except-when-theyre-not-part-2/</link>
			</item>
	<item>
		<title>Exceptions are Easy.   Except when they&#8217;re not.</title>
		<description><![CDATA[Assuming all the code compiles correctly, is Foo.Load() exception safe? Is there anything I need to change in Load&#8217;s exception handler to insure an instance of Foo is always in a valid state? 

///Defines a type that associates a URI with the
/// count of frobs, miscellaneous information about those frobs
/// and where to get them.
///
public [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/exceptions-are-easy-except-when-theyre-not/</link>
			</item>
	<item>
		<title>Encapsulating Your Way To Better Unit Tests</title>
		<description><![CDATA[I an earlier blog, I discussed the qualities of good unit tests.  Primarily, good unit tests are fast, isolate the bugs, repeatable, self-validating and timely.    
At first blush, that seems easier said than done.  We write distributed software and connect to databases.   Some of those databases live in [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/encapsulating-your-way-to-better-unit-tests/</link>
			</item>
	<item>
		<title>Qualities of Good Unit Tests</title>
		<description><![CDATA[So &#8212; you&#8217;ve been tasked with insuring your code has unit tests.   What does that mean, really? 
According to Wikipedia,
unit testing is a software design and development method where the programmer gains confidence that individual units of source code are fit for use. A unit is the smallest testable part of an application. [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/qualities-of-good-unit-tests/</link>
			</item>
	<item>
		<title>Why Unit Test?</title>
		<description><![CDATA[Nobody changes until the pain of staying the same becomes greater than the pain of change ~ Anonymous
If the code I come across in my work is any example, most developers haven&#8217;t drank the Unit Testing Kool-Aide.   Given the old saw about change and pain, I can almost understand. Almost.
So, why should I [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/why-unit-test/</link>
			</item>
	<item>
		<title>Is Your Code SOLID: The Dependency Inversion Principle</title>
		<description><![CDATA[The mother of all SOLID principles.  Nail this one, and you&#8217;ll keep your codebase supple &#8212; ready for just about any change you throw at it.   The Dependency Inversion Principle comes in two flavors: 

HIGH LEVEL MODULES SHOULD NOT DEPEND UPON LOW LEVEL MODULES. BOTH SHOULD DEPEND UPON ABSTRACTIONS. 
ABSTRACTIONS SHOULD NOT [...]]]></description>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/is-your-code-solid-the-dependency-inversion-principle/</link>
			</item>
</channel>
</rss>

