Beware of coder "Joe"!

[Blue_Angel]

I'd like to report a situation which I had with a registered member of this forum, his name is "Joe", his email is: roulettecoder@tutanota.com
He also has a website which is linked on his signature.
The said person did program for me several methods over the course of 2 months approximately.

He begun without any issues and I always paid on time, until after he had already program 5-6 methods, he made a "bugged" program, this technical issue was not minor, I couldn't simulate, neither use it for live betting.
On the top of this he also failed to address my consistent efforts to get in touch with him and fix it, as he has promised about any bug related issues would fix free of charge regardless of hoe many of them.

Another program didn't have any "bugs", but was mistakenly interpreted, after many days of instructions, explanations and examples, after he already programed for me several other methods, on this final one he was UNABLE to understand and implement the crystal clear instructions which I've meticulously described for so many times!

Was that in purpose? I don't know, but the result remains the same!
He ignored completely my pleas for fixing the already paid programs!
After all it's not about the amount of money involved, that's insignificant, it is about ETHICS and HONESTY!

[Steve]

I've been dealing with programmers for a long time. What you described is a common situation. I don't know the exact details of your situation, but have this advice for anyone hiring a programmer:

1. Give crystal clear explanations INCLUDING:

a. Algorithms (the actual calculations, with examples)
b. Flow charts (so they understand what the software does in each situation)
c. Diagrams and images (show the interface you have in mind)
d. Tests they and you must both do, to ensure the program does exactly what you need. Have them code clear logs for you to examine. You can remove the logs when you've finished testing.

2. Have clear contracts which outline:

a. Pricing structure (hourly rate or fixed price)
b. Exactly what's included (ie bug fixing, and the time limit for you to report bugs)
c. Source code (including any libraries)

Overall it's best to outline very clear milestones. Basically give a deposit to start, then pay each milestone after you've seen the progress needed. After payment, get the current source code and back it up). NEVER pay up-front or before a milestone is complete - if you do, they'll drag their feet and become lazy.

3. Cheaper is not better

If you pay a cheap programmer, if the program is complicated, they'll probably make a mess of it. development can take longer, and become even more expensive. That's because they may be a crap and slow coder. And later you may hire a more competent programmer to clean up their mess. If that happens, it may be more viable to start from scratch.

4. Experience is not everything

A programmer can have a great profile and lots of experience. But if they aren't motivated and with a good work-ethic, they could be problems later. Always carefully check their profile to ensure they also have the right skills and experience for what you need.

There's more to it, but those are the basics.

[Blue_Angel]

 I could not agree more.