Quote:
Originally Posted by zagi
Just going to fill in my 2 cents here, before flying out somewhere and meeting up with someone - I would write up a complete project spec to the best of your ability.
It will help you see your vision better and allow the coder some time to prepare. You can even quantify various coders against each other by asking them to evaluate your spec and propose their solutions/algorithms or even uncover problems with your design.
You may be able to get away with brain storming together but I think the better approach is to invest some hard work up front before getting a third party involved. In my experience the meetings tend to go well - but the end result does not deliver. What really surprises people is that everyone says: 'Yes, it'll take 1 - 3 weeks' and before you know it its month 4 and you're still not done.
Without a well thought out and written plan I don't think getting in face time will make a difference. Your mileage will vary.
|
Well put.
The biggest disconnect for me comes between concept, and conception. Almost like I need a project manager who knows code, design, etc. so that they can take my not techie, improper use of geek terms, and put them into a version techies understand.
I explain to any coder, or designer, I am not a techie like them. So do not expect me to use the 'lingo' right. Some are very good. They can piece together from their many clients, and have excellent communication skills.
The vast majority are ego maniacs, who are anal retentive's about using the right slang, and will go into a whole dissertation on why a code should be done one way, or another, and why (fill in the blank)'s code is shit, blah blah blah.
All of which means little to somone who has no idea what they are talking about.