![]() |
This is a new wrinkle for me: telling other programmers what to code. Additionally, the idea of offshore development brings up so many questions for me. Is the project size appropriate to the budget allocation? How does copyright, patent and intellectual property protection in India affect us? How will day-to-day interaction and management occur? Would day-to-day contact be necessary? What do I tell my friends, the developers that we laid off and we aren't hiring to help?
Now, I've written functional specs for me and for non-programmers, but never a technical spec for other coders. And I appreciate the importance of specs, particularly in this situation. As Joel says, "when you design your product in a programming language, it takes weeks to do iterative designs."
There are at least two programmers who read Massless, right? If you have any links or ideas or stories about creating a spec for offshore dev teams, I would sure appreciate an email. Otherwise it's Google-and-newsgroup hunting for me.
Reportedly, in the south of India, shaking your head from side to side means "yes."