It's just new and with glitches... purveyors are always in a hurry to "get it out there"... before it's ready for prime time. Years ago when I was an insurance broker... if a company announced "new software" it was always 18 months of SNAFU.... to be avoided until they had the time to fix things. "New software" is a curse for high-volume traffic.
Why Trading softwares breakdown when they are upgraded
- Thread starter gmst
- Start date
It's just new and with glitches... purveyors are always in a hurry to "get it out there"... before it's ready for prime time. Years ago when I was an insurance broker... if a company announced "new software" it was always 18 months of SNAFU.... to be avoided until they had the time to fix things. "New software" is a curse for high-volume traffic.
Nothing positive to offer? We are waiting for you to offer some facts since you said you have insight.
Why do you want me to tell you how many lines of code Ninja's complete src has. You said that you know that it's all written piss poorly and highly unorganized etc. How do you know, 1st grader?
Well I guess if people like you work for a trading software, then I am close to getting my answer.....the answer seems to be that these programmers are just not good enough....
....LOLOLOLOLOLOLOLOLNow read below so that you will understand:
All other folks who have commented on this thread understood that those 3 points I raised in my 1st/2nd post (including the point that said "piss poorly and highly unorganized code") are possible hypothesis as to why trading software suffer so many glitches post an upgrade. They are not at all authoritative statements since I am a novice in software development field. My aim with this thread was that: I wanted to hear views of more experienced members on this forum to get answers to my questions and also to slightly increase my understanding of software development process.
But, you have a reading comprehension problem that you confuse the hypothetical things that I mentioned in my first 2 posts as authoritative comments or insights. HAHAHAHA
AFAIK a standard English question reads as following example
1) DO Trading software vendors do very limited testing compared to MS?
2) ARE Programmers who work for Ninja, TS, MC, Amibroker, Sierra etc. piss poor programmers and DO they write highly unorganized and error prone code compared to programmers working for bigger non-trading software firms?
etc.
Yeah, you are a true master of nothing.
1) DO Trading software vendors do very limited testing compared to MS?
2) ARE Programmers who work for Ninja, TS, MC, Amibroker, Sierra etc. piss poor programmers and DO they write highly unorganized and error prone code compared to programmers working for bigger non-trading software firms?
etc.
Yeah, you are a true master of nothing.
These are still generalizing claims. Where are your facts about ALL trading softwares? Where are your tests?
InterestingUser
one final comment for you to think a little bit.....
If you work for a trading software vendor (and I don't care whether you are with Ninja or MC or TS or Sierra or IB or anyone else), instead of fighting with me on this thread, you should seriously think about the issues I have raised as a customer in this thread.
If you are smart, you will show this thread to your management and they will hopefully recognize that this deficiency in delivery of your product, is actually a great opportunity to improve processes at your firm such that 6 months to 1 year down the line, you guys start to get a reputation in the trading software market that your product does not breakdown after an upgrade.
Please Please Think about this post.
one final comment for you to think a little bit.....
If you work for a trading software vendor (and I don't care whether you are with Ninja or MC or TS or Sierra or IB or anyone else), instead of fighting with me on this thread, you should seriously think about the issues I have raised as a customer in this thread.
If you are smart, you will show this thread to your management and they will hopefully recognize that this deficiency in delivery of your product, is actually a great opportunity to improve processes at your firm such that 6 months to 1 year down the line, you guys start to get a reputation in the trading software market that your product does not breakdown after an upgrade.
Please Please Think about this post.
I don't have a software company and don't work for any one. I want to know where are your facts. You made claims. IF you make general claims you need to provide facts. Anything else is a joke.
Pointing to a specific software and its problems is a specific case but not a general fact that applies everywhere.
EDIT: I'm smart, yes. But I very much doubt that you are.
Pointing to a specific software and its problems is a specific case but not a general fact that applies everywhere.
EDIT: I'm smart, yes. But I very much doubt that you are.
You created a new alias just to reply to this thread, till now you have made 8 posts and all on this thread, from your posts it is clear that you took offense from the words piss poor programmers......and you say that you don't work for a trading software vendor!!!Dude ----
Anyways, no offense but after interacting with you and from contributions of others on this thread, I now know why RETAIL trading software suffer from so many problems during an upgrade and these are:
1) Very limited testing
2) Piss poor programmers like you
Non-genius, perhaps I have used some more softwares unlike you. "Contrary to you" I don't know their source codes. And contrary to your general "facts" some are solid to very solid and some are less and some are even more unstable than they are stable most of the time.
Big difference to your generalizing hyperbole.
You know. Yeah, of course you know and you also know how to correctly formulate a rock solid English question. Right!
I once used a large, publicly-traded brokerage whose online trading infrastructure (a java-in-the-browser client communicating with servers using some proprietary TCP/IP-based protocol) would occasionally break down for hours at a time. Many complaints on Yahoo message boards, but it always surprised me that the breakdowns rarely made the financial news, and the company continued getting 100,000+ DARTs. I can only assume that the customer base that used this application was very small, and most trades were placed by financial advisors using some other, more reliable, platform.
The point is that retail traders may be a very small part of the company's customer base, possibly numbering only several thousand. That means there may be perhaps a dozen or two developers devoted to this software. Bugs will slip through. Bugs are a lot less likely in things like Excel, where there are perhaps 200 million customers and a suitably large development staff.
The point is that retail traders may be a very small part of the company's customer base, possibly numbering only several thousand. That means there may be perhaps a dozen or two developers devoted to this software. Bugs will slip through. Bugs are a lot less likely in things like Excel, where there are perhaps 200 million customers and a suitably large development staff.