views:

115

answers:

5

This is inspired by the question, "What to do with a home server?"

So far I can think of:

  • A continuous integration build server, like luntbuild or cruise controll
  • Source control
  • A bug tracker/process tracker
  • A copy of all the artifacts you have on production

What about:

  • An IDE and remote desktop? (Although personally I think IDE's are still best on a client)
+1  A: 

A debugger of some sort...

jle
+2  A: 
  • A web server
  • A script to migrate from dev to test
  • A script to migrate test to production
  • a script to backup your svn to S3 or similar offsite backup storage
  • vi/vim because you are going to need a good text editor
  • sed, awk and ruby for the really hard scripts
MikeJ
+3  A: 

Local wiki server for documentation, notes, etc.

David Plumpton
+1  A: 

valgrind and/or other profiling software

Marco van de Voort
+1  A: 

postmortem debugging tools, for Windows that is:

  • umdh (for memory leaks)
  • drwtsn32 (for crashes),
  • cdb (to get minidumps from hung apps),
  • windbg (to inspect the minidumps).

Also put a symbol server on there to store your own app's symbols (without having to remember which set correspond to which version of the app)

These are all things to help debug apps as if they were run on a customer machine - not your development machine with its debugger, sources, symbols etc. If you can diagnose problems there, you can take the tools onsite to fix problems you'll never see when you run them at home.

Also put a file share on and store all the installers for development tools you'd use - so you can easily get all the bits you need to set up a new development workstation.

gbjbaanb