Contents tagged with Development
-
The “Why To” Manual
Hank Wallace turned me on to a post by Allison Shapira where she summarizes a key point from Rob Walker's writeup of the Blue Man Group - the "Why To" manual.
-
Miško Hevery on Writing Testable Code
Miško Hevery has written a great summary of some basic coding rules for testability in his post Writing Testable Code.
-
The Last Language War / Language Trolling Post You'll Ever Need To Read (Hopefully)
Via Jeremy D. Miller
-
Jim Highsmith on the Chaos reports
Max Wideman got permission to reprint Jim Highsmith's article The Chaos Report - Reality Challenged.
-
What Do You Need To Know?
Time to vent. I’ve been trying to hire a couple of senior developers on a team that is primarily building a web based framework (i.e. software for developers). I have some minimal expectations for a senior developer that I don’t think are all that outrageous.
-
HanselMinutes #4
Scott Hanselman has started a podcast called HanselMinutes to talk tools and utilities. Episode #4 on Continuous Integration caught my attention because of 2 names mentioned during the discussion of the Ruby Watir library. Both Dustin Woodhouse and Travis Illig got mentioned because of tools they have written to integrate the Watir functionality at development or test time. Travis wrote RubyTestExecutor which hooks Ruby/Watir scripts up with NUnit. Dustin wrote WatirNUt which is a utility that creates a portable, testable NUnit binary wrapper around Watir test scripts and supporting files.
-
[Article]Simplify Data Layer Unit Testing using Enterprise Services
Roy has a really nice article that addresses the problem of testing data access code. The only thing is that it is missing a really important step assuming you are using object like views, stored procedures, user defined functions, rules, etc. I've been bitten in the past often enough ignoring this issue that I make sure I pick an approach rather hoping it just works.
-
International Addresses
Darrell pointed me to this site on International Addresses and the complexities therein.
-
Together Developer for Visual Studio.NET
Borland has released a version of Together Developer that integrates into VS.NET. Check out the screen casts. I'm thinking that Together combined with ReSharper from JetBrains could be one killer combination.
-
Build Servers - Love 'em & Hate 'em
Jim Shore wrote about why he doesn't like Cruise Control. I agree to some extent with his points that the reason teams use it is to catch build errors and deal with "slow" builds. Having implemented both Draco.NET and CruiseControl.NET and toyed with FinalBuilder I am not overly impressed with any of them. My impression is that I spend way to much time fiddling the build server for the value added. I will say that I would still implement a build server for any team for the single reason that "people are fallible". People forget to commit related changes, or add files to CVS, run tests, etc. The build server never does.