Thank you very much for your reply. I got some great pointers from your article, and I look forward to chatting with the developers and casually bringing up some of the points you mention.
I'm interested in your proposition - if they don't have an SVN repo and bug tracking systems they're not real developers.
Are there any other very clear indicators that these aren't the guys you want on your team?
Co-incidentally, if I do need to setup this kind of environment, do you have any recommendations on the software infrastructure I should use?
Very interesting perspective - I've tended to work with people by doing big picture proposals with a list of deliverables, but this kind of bite-size requirements could be a great way to get a feel for the team.
This could even become my standard way of working with coders.
Thanks! I'm an IT guy at heart myself - Dilbert style management makes me break out in hives.
Appreciate the feedback on the milestones. I'm very interested in what a coder would generally consider to be best practices in a software rollout, and how to keep people interested, motivated and on track.
Thank you very much for your reply. I got some great pointers from your article, and I look forward to chatting with the developers and casually bringing up some of the points you mention.
I'm interested in your proposition - if they don't have an SVN repo and bug tracking systems they're not real developers.
Are there any other very clear indicators that these aren't the guys you want on your team?
Co-incidentally, if I do need to setup this kind of environment, do you have any recommendations on the software infrastructure I should use?