Jeremy D. Miller -- The Shade Tree Developer

Browse by Tags

• Database and Persistence
• Legacy Code
• Maintainability
• Pair Programming
• Ranting
• Starting a new Project

• What about Usability?

  Sort of a continuation of the ongoing maintainability series, it's time to look at some of the benefits. And rant because that's just what I do. After publishing My Programming Manifesto (about the things *I* was thinking about at the time) post... Posted Jan 14 2007, 10:16 PM by Jeremy D. Miller with | with 5 comment(s) Filed under: Maintainability, Continuous Integration, Test Driven Development, Ranting

• Week 2: Scheduling and Coordinating the Work

  Continuing the " Getting Started " series. My team just finished our second week. Luckily enough we were able to get through release planning quickly and start Iteration #1 on Tuesday. CruiseControl.Net is up and running. I kept a list of the... Posted Oct 15 2006, 11:05 AM by Jeremy D. Miller with | with 2 comment(s) Filed under: Continuous Integration, Test Driven Development, Starting a new Project, Pair Programming

• Week 1 Questions: How do you organize your NUnit test code?

  I can see more of these little posts about setting up a project coming up, so I made a new category called " Starting a new Project ." My team discussed how we were going to organize the NUnit TestFixture code. We talked through the normal options... Posted Oct 07 2006, 08:32 PM by Jeremy D. Miller with | with 18 comment(s) Filed under: Continuous Integration, Test Driven Development, Starting a new Project

• Creating a Maintainable Software Ecosystem

  The blogosphere is full of discussions and arguments on the best way to write and design software. It might be worth the effort to stop and go back to first causes -- just what quality or qualities do we want in our code? What are we trying to achieve... Posted Aug 13 2006, 09:49 PM by Jeremy D. Miller with | with 23 comment(s) Filed under: Continuous Integration, Legacy Code, Test Driven Development

• Database per Developer and Environment

  Our Continuous Integration talk Monday got a bit rushed at the end and I missed an important point when we talked about CI with databases. For the love of all that is good and holy in the world create a separate database/schema for: Each development workstation... Posted Sep 21 2005, 04:03 PM by Jeremy D. Miller with | with 13 comment(s) Filed under: Continuous Integration, Database and Persistence, Ranting, Test Driven Development

• How Agile practices can help staunch the flow of defects

  I was in a project retrospective meeting today, and I’ve got another one tomorrow. I think we had a fairly low rate of defects compared to the complexity of the code, but we had some definite inefficiency in the amount of time it took us to detect and... Posted Aug 25 2005, 08:39 AM by Jeremy D. Miller with | with 9 comment(s) Filed under: Continuous Integration, Test Driven Development

• Testing Granularity, Feedback Cycles, and Holistic Development

  So far this year I've done a greenfield development project, made changes to a legacy application, and am about to take over development on a third product. The new code was built with Test Driven Development and Continuous Integration from the beginning... Posted Aug 17 2005, 08:20 PM by Jeremy D. Miller with | with 15 comment(s) Filed under: Continuous Integration, Test Driven Development

• Using Continuous Integration? Better do the "Check In Dance"

  So you're making the move to install a Continuous Integration process on your project. Most of your early attention is going to be spent on getting the CI server up and the build scripts put together and functioning. That part of the process in the .Net... Posted Jul 25 2005, 03:03 PM by Jeremy D. Miller with | with 23 comment(s) Filed under: Continuous Integration, Test Driven Development

• Resources from the Continuous Integration talk last night

  If you were at the Continuous Integration talk last night at the Austin SPIN, here is the set of resources I mentioned. The slides from the presentation are here or at http://www.jwspro.net/aspin/ . Thanks for coming out last night in the rain and putting... Posted Jul 15 2005, 07:16 PM by Jeremy D. Miller with | with 3 comment(s) Filed under: Continuous Integration, Test Driven Development

• Taming the Legacy Beast - Dose It With Some NAnt

  Yesterday I griped about legacy code. I carped about VSS, whined about the tight coupling, groused about the arcane configuration setup, and spewed invective about the stupid manual post compilation steps it took just to make the code work. Today it's... Posted Jun 27 2005, 06:24 PM by Jeremy D. Miller with | with 2 comment(s) Filed under: Continuous Integration, Legacy Code, Ranting, Test Driven Development