Should I only hire coders I can sit in the same room with?
That will probably work best, but it will cost more.
Have you ever managed a programming team before?
I haven't. Any pointers?
Not really. Just be prepared for the programmers to misunderstand the
specification at every turn.
Great advice from everyone, thank you. By hiring coders, the
intention is to save myself time and effort but it sounds like I would
only be replacing one problem with another.
I hope I wasn't too discouraging, but you're definitely replacing one
problem with another.
I don't need
On Thursday 11 November 2010 17:33:25 Grant wrote:
Have you ever managed a programming team before?
I haven't. Any pointers?
Good grief! The literature is full of weighty tomes on the subject, and
copious advice is available in multiple news groups - and no doubt e-
mail lists too by now.
Grant, you need to stop being paranoid. ?I am surprised you even
worked up the courage to let slip on here, in public, that you even
have a sooper dooper sekrit project.
This seems to be the general consensus. You see, I don't have a
computer science degree and about 75% of what I know
Am 10.11.2010 06:56, schrieb Grant Edwards:
On 2010-11-09, Florian Philipp li...@f_philipp.fastmail.net wrote:
Well, there are two ways to go here:
1. Modularize what you have. Give every developer only the source he
is supposed to work on and binary interfaces (libs + header files
Read the OP again. He wants to obsfuscate the code to make it
unreadable for the people he's hiring to work on it.
It would be simpler and cheaper to hire developers who don't
understand programming language in question, computers, programming in
general, or even english.
Then don't let
On 9 November 2010 09:14, Grant emailgr...@gmail.com wrote:
Theoretically, a modularized software project will be more easily
assembled by large teams, since no team members are creating the whole
system, or even need to know about the system as a whole. They can
focus just on the assigned
Theoretically, a modularized software project will be more easily
assembled by large teams, since no team members are creating the whole
system, or even need to know about the system as a whole. They can
focus just on the assigned smaller task.
On Tue, Nov 9, 2010 at 9:14 AM, Grant emailgr...@gmail.com wrote:
Read the OP again. He wants to obsfuscate the code to make it
unreadable for the people he's hiring to work on it.
It would be simpler and cheaper to hire developers who don't
understand programming language in question,
Only expose the teams to what they need, give them prototypes and
discriptions to the other parts. Like a man page.
On Nov 9, 2010 12:16 PM, Grant emailgr...@gmail.com wrote:
Read the OP again. He wants to obsfuscate the code to make it
unreadable for the people he's hiring to work on it.
It
On 9 November 2010 10:08, Grant emailgr...@gmail.com wrote:
It sounds like I'm really going against the grain here. Is it
standard practice to hire a developer on the internet from any given
country, never meet him or her, have them fax a signed NDA, and turn
over your biggest asset to them?
Apparently, though unproven, at 20:08 on Tuesday 09 November 2010, Grant did
opine thusly:
It sounds like I'm really going against the grain here. Is it
standard practice to hire a developer on the internet from any given
country, never meet him or her, have them fax a signed NDA, and turn
Am 09.11.2010 19:08, schrieb Grant:
Theoretically, a modularized software project will be more easily
assembled by large teams, since no team members are creating the whole
system, or even need to know about the system as a whole. They can
focus just on the assigned smaller task.
13 matches
Mail list logo
