(How To) Hire A Programmer?What Precautions?
- Thread starter jonnyy40
- Start date
Major issue:
Software development is such as esoteric field...
That I do not see how a non-engineer...
Could even evaluate programming talent.
One is very likely to have mediocre people bullsh*t you about what they can do...
And waste your time/money.
You can take that to the bank...
cj...
exactly.
I would say that wareagle's approach makes most sense, not only for security.
I also think that there is a difference between software that "just works" and software that will be enhanced in the future. One of the biggest issues in software development is maintainability of the code: scalability, readability, good design, etc. That, in my opinion, is a major feature of the talented programmer.
You can take that to the other bank...
cj...
I don't know why, I missed this one.
Jonny, I want to say that once more: don't talk to people you don't know, specially if you want a long term relationship.
You are a trader aren't you? Would you advice someone to give money to invest
to someone unknown? Even if with credentials?
Think about it.
If you don't have someone you trust, find one. Don't rush
The thought that goes into the design up-front is critical. Too often non-programmers don't express themselves with enough clarity to make the development worthwhile. As a hired-gun it isn't bad, as this just adds time and cost to the project which presumably you are being paid by-the-hour to do. But as far as getting the project done, lack of clarity is up-front and often unintended sabotage.
If you understand the crucial parameters of the system, it pays to have those created as inputs to the system. Unless the basic logic of the system changes, you should be able to control aspects of it without resorting to a re-code.
Again, it depends on what you are programming in. Each platform has it's own idiosyncrasies, language or data-wise, that only experience will identify. You may trust someone who can code, but if they have no experience with a particular environment, you are asking them to devote time to learn it. Time is money, and time ain't cheap.
If you understand the crucial parameters of the system, it pays to have those created as inputs to the system. Unless the basic logic of the system changes, you should be able to control aspects of it without resorting to a re-code.
Again, it depends on what you are programming in. Each platform has it's own idiosyncrasies, language or data-wise, that only experience will identify. You may trust someone who can code, but if they have no experience with a particular environment, you are asking them to devote time to learn it. Time is money, and time ain't cheap.
YOU need to first put your ideas down on paper in the form of funtional and design specifications. Then once you find a developer, they will have something with which they can design an appropriate architecture around.
Don't forget the legal issues of intellectual property and nondisclosure.
Don't forget the legal issues of intellectual property and nondisclosure.