When I'm a new team member

Jsut had a meeting about how to improve the build process for the team - the current structure of the code in the source control system means I can't just get the code out and build it - this to me is the sign of a failing project\team!

I believe every project should be structured so that the following use cases are valid for any new developers coming onto a team, there's nothing more demoralising to new team members when you have to some kinda of voodoo to get a project to build;


As a developer I want to install the IDE So that I can compile source code.

As a developer I want to install the source control client So that I can extract code for compiling.

As a developer I want to compile the code So that I can verify the code compiles sucessfully.

As a developer I want to install a unit test framework So that I can execute unit tests for the code.

As a developer I want to execute the unit tests for the code So that I can verify the tests execute successfully.


Now this is not about being able to the run the application in a local debug build this about being able to confirm I'm standing on firm ground and I'm ready to start making changes to code base with confidence. (because the unit tests are all successful). For me one of the reasons for unit testing is to give team members & new starters the confidence to change code I've written without requiring my hand-holding.

There's nothing worse than being a new team member and not being productive ASAP.



Awkward Coder