The truth is that our consultants are a highly professional group of individuals and your one bad experience does not warrant your negative generalization. Tyler has been a dedicated NinjaTrader partner for a very long time and our mutual clients have had nothing but positive feedback for him. You yourself sent my team praise for your experience with Tyler not even a week ago?
As for your assertion that we gave you bad support in this case, that could not be further from the truth. My team has acted as an arbiter between you and Tyler delicately trying to foster a resolution but the short story is that you did not like any of the compromises he gave you and proceeded to threaten him with negative publicity after which he decided that he would not longer deal with you. Bridge burned.
The following 9 users say Thank You to NinjaTrader for this post:
Please be careful with what you are writing.
This coder has maybe done something wrong, and his answer is maybe not appropriate, but this can happen on both sides.
Like few others here I'm coding strategies for guys, and had to deal numerous times with:
- bugs on my side (nobody is perfect ),
- wrong definition from the customer,
- customer changing specifications after each delivery,
I know it's very hard for the coders to deal with traders, mainly with traders who never did this kind of things (project specifications).
I don't say it's the case here, but this is what we see all the time.
What I'm usually doing, with potentially unhappy customers, or when I understand it will take weeks to really understand what they want: I don't take the job, or refund everything if I already starts and delivered something.
This is what should be done here but the coder here, but it's also not great to spend hours on something, and don't get paid at all.
I had a "problem" like this with a futures.io (formerly BMT) member: creating a complex strategy, which was working. Then he asked to add few "simple" things, which were in fact very hard to do and to debug. I spent dozen of hours to find what was wrong with the new functionalities (that was only undocumented/unsupported Ninja functions), and when I finally found where was the problem, the customer did not want his stuff anymore (means $0 for me)!
Now, maybe the coder himself could explain his own point of view ?
Usually in trading, those who know don't talk, and those who talk don't know. (Al Brooks)
success requires no deodorant! (Sun Tzu)
The following 7 users say Thank You to sam028 for this post:
Well, now you have a negative feedback! The reality is that my project was a little bit complicated and he just COULDNīT DO IT! this is the undisputed TRUTH about this story! He didnīt fulfill his promise about the script, nor he fulfiled his promise about the moneyback guarantee. those two are FACTS andUNDISPUTED TRUTH.
Another TRUTH is that your team couldnīt make anything about that. I still do not have a fixed script, nor any money and on top of that he is still one of your consultants and next time when a guy like me purchase him a more complicated project, the result will be the same.
This thread is started, because people has to know the truth and they have to have the right expectations when they have to pickup a consultant from your list.
Thank You for your post, it is realy precious and 100% related to this thread.
The same thing happened with us, I asked him for new functionalities(it is described in my 1st post) and he was thinking, that the bugs come from the new functionalities. Since we were in a fight already, he didnīt want to proceed, refunded me the money for the add ons and said that he lefts me with the first version of the script that I was happy with! OK, I totaly agree with that, but we found that the 1st version has to be debugged and it is still in his obligation to fix that(exactly as you described), but he refuses to do that and doesnīt answer to my e-mails.
We alsow tried another thing, since he is offended to me, than to start communication with my friend whos money where alsow in this project, but Tyle refuses communication with him alsow ..
I reached an agreement with a programmer for a custom job at a mutually agreed to price. The project ran into unforeseen problems. The programmer was getting very frustrated. I sent him additional funds and he made the program work.
Did I pay more than I had agreed to? Yes
Do I have a program that still works? Yes
If I contact him today, will he help me? Yes
At this point you no longer have the option I had.
1. I would suggest you turn down the heat so you don't scare off others that may be willing to help you out.
2. I'm not sure it is realistic to expect another professional programmer to clean up someone else's mess for free , especially since you have posted how much money you gave to the first programmer for code you are unhappy with. Translation: Be prepared to spend more money.
3. If board members offer to help you, accept their assistance and be gracious. Translation: Tell them thank you and quit screaming "All Programmers are scum".
4. Get 3 quotes before awarding work to a contractor.
5. I wish you success in your future endeavors.
I'm just a simple man trading a simple plan.
My daddy always said, "Every day above ground is a good day!"
The following 4 users say Thank You to ThatManFromTexas for this post:
I have used Tyler for several projects - some very simple and some very complicated. He has been professional and delivered on all of them. He has always worked with me to resolve any issues and the code he has delivered has worked very well. I have asked for quotes from other programmers and they either send you an agreement that says they now "own" the code or upon further investigation are "programmers" that also sell trading software. It is difficult to share trading ideas with a programmer that sells trading programs. Tyler is a programmer that works with you to develop your trading ideas.
I've worked on some simple things as favors for friends even though I only know what little I know by picking through other people's code.
After a while I asked them to write out the logic in pseudo-code, because they invariably would leave out things. After looking through what they wrote, I would usually ask "but what if..." to try and fill in the holes before even starting.
It was pretty frustrating, but I wasn't getting paid, so there was never a dispute.
If the code is well-written and commented, you may be able to pick through it and isolate/correct where the error(s) occur. Since it is using some undocumented features, that's going to require deeper digging.
It might be worth it though, because then you will be less reliant on an external source to code your ideas.