evolve2k · May 15, 2012 14:31
diff --git a/gistfile1.txt b/gistfile1.txt
 1. Utilise a good programmer task management tool
 I strongly recommend you utilise pivitol tracker.
 Have the developer keep the tasks they are working on up to date and ask them to communicate with you through pivitol tracker.

 2. Have the developer keep their source code in an online repository that you both have access to all the time.
 I strongly recommend that the code is kept at github.com in a private repository that you maintain. 
 (It will costs you aprx $9 per month to do so).
 Have the developer tag each batch of code they work on with the specific task(story) they are working on at the time.

 3. Ensure your developer writes tests.
 Cucumber tests are good as you'll be able to read and understand them.
 Also RSpec tests should exist at least one file for each object/model that exists.
 Eg in the example where the object 'Game' existed, I would expect to see a file with some tests showing what a game should do.

 4. Have someone on your team maybe keep a skype chat open with the developer, so they can ask domain questions as they arise if need be. The more you are available to answer questions the less stupid assumptions the developer makes and the better your code is straight up.

 5. Break down the job into small chunks, spend your own time prioritising the order of what should be built next, Pivotal Tracker is great for this, it helps the developer be efficient also knowing exactly what to work on next. Nothing more painful than starting task 5 and then everyone's like, no no we want you to stop everything and work on task 8.
	1. Utilise a good programmer task management tool
	I strongly recommend you utilise pivitol tracker.
	Have the developer keep the tasks they are working on up to date and ask them to communicate with you through pivitol tracker.

	2. Have the developer keep their source code in an online repository that you both have access to all the time.
	I strongly recommend that the code is kept at github.com in a private repository that you maintain.
	(It will costs you aprx $9 per month to do so).
	Have the developer tag each batch of code they work on with the specific task(story) they are working on at the time.

	3. Ensure your developer writes tests.
	Cucumber tests are good as you'll be able to read and understand them.
	Also RSpec tests should exist at least one file for each object/model that exists.
	Eg in the example where the object 'Game' existed, I would expect to see a file with some tests showing what a game should do.

	4. Have someone on your team maybe keep a skype chat open with the developer, so they can ask domain questions as they arise if need be. The more you are available to answer questions the less stupid assumptions the developer makes and the better your code is straight up.

	5. Break down the job into small chunks, spend your own time prioritising the order of what should be built next, Pivotal Tracker is great for this, it helps the developer be efficient also knowing exactly what to work on next. Nothing more painful than starting task 5 and then everyone's like, no no we want you to stop everything and work on task 8.
No results found