Cloud Computing and Enterprise POJOs
Chris Richardson

Run Java Applications on Amazon EC2

My book

Calendar

««Jul 2009»»
SMTWTFS
    1234
567891011
12131415161718
19202122232425
262728293031

My Top Tags

                                                                               

My RSS Feeds








 

I am the founder of Cloud Foundry, which provides automated, outsourced data center management for Java applications on Amazon EC2.

I am the founder of Cloud Tools, which is an open-source project for automating the deployment of Java and Grails applications on Amazon EC2.

I run a training and consulting company that helps organizations build better software faster and deploy it on the cloud.

We provide a variety of services including:

  • Development - we can build your application for you
  • Deployment - we can find a hosting partner or deploy your application on Amazon EC2
  • Training classes for Spring, Hibernate and Acegi Security
  • Jumpstarts to get your project off to the right start
  • Reviews to improve your architecture, code and development process

For more information contact me.

 

My bookmarks

Mailing List

Leave a broken test - a great example of why that's an excellent idea

« H E email
posted Monday, 12 November 2007
Today, I was reminded why it's a good idea to end a programming session with a failing test (suggested by Kent Beck in his TDD book). Last week I went to the excellent QCon conference and hadn't worked on my client's application since Tuesday. As you might expect, my memory of what to work on next was a little hazy. But when I fired up Eclipse, I was greeted with a broken web test. I'd actually stopped work in the middle of writing the test so it wouldn't compile, let alone run. This was an instant reminder of what I'd been doing. As a result, I was able to immediately carry on from where I'd left off.

tags:                

links: digg this    del.icio.us    technorati    reddit


comments (3)


1. Andreas Guther left...
Sunday, 25 November 2007 5:52 pm

This is one of those so simple but very effective tips out of Kent Beck's rich treasure box of coding habits.

Of course it only makes sense if you do not check in your code into your Source Control Management system before you leave, assuming that you are integrated into an automated, continuous build system that also executes tests.


2. Chris Richardson left...
Sunday, 25 November 2007 6:25 pm

Yep. You don't want to check in your broken test. There's the assumption that you end the programming session with unfinished work (that you wouldn't want to check in). The broken test is the reminder of what you were working and what to do next.


3. sehe left...
Monday, 30 June 2008 11:49 am

Or you can use a distributed VCS and have all the safety and convenience of version control while you have no working change-set yet. I use Bazaar, but it sounds like Git, Mercurial and possibly Darcs might be just as good if your platform allows it (Bazaar runs on all my platforms and is unique that way, afaik)