Search results

An exit strategy would be to wait for a reversal bar and close or reverse your position. Example: You are long, sell when the current bar closes below the previous bar. You could also reverse your position and get short at this time. As with any method you will get stopped out and...

Method: Wait for the current bar to close above (below) the previous bar. If close above, go long with stop below low of bar. If close below, go short with stop above high of bar. No, I haven't backtested this, but it is the essence of simplicity. Since the markets are fractal in nature...

Don, I'm intrigued by your opening collar strategy. However from a purely subjective viewpoint, it seems that more than 50% of the time, up days have higher openings and down days have lower openings. I'm just concerned that trying to take the other side of the momentum will put me on the...

If I have a bullish or bearish bias on a stock, should I still try to collar the opening and then exit quickly, or can I try to initaite a position and ride the momentum from the previous day? For example: if I'm bullish and think more buy than sell orders will come in overnight, should I...

Since high and low are only relative (except for zero) I think a better question to ask is how to spot a reversal from a recent trend. Oscillator indicators are best for this. My favorite is RSI. When RSI goes above/below a threshold value I define, then I look for price to cross over a MA as a...

Support and resistance for the current time period can be calculated from the previous time period (high/low/close) by using pivot points. Pivot points will not usually correspond to the peaks and troughs on a chart however, if that's what you wish to define.

Actually, I agree, but in the sense that a shorter lookback period SMA can give similar performance to a slightly longer EMA. Obviously when keeping the lookback periods the same, the EMA is more responsive to current data.

When you normalise historic data, you must generate a relative strike, a relative IV, and be consistent in the time until expiration. Have a look at the file I have attached. When I say surfaces are stable over time, look at the current surface for the December contract of your choice, and...

By comparing the current surface to the historic surface, you can get an idea if an option is being mispriced, or that an event in the underlying is possibly about to unfold. Of course to build a historic surface, one must properly normalize the data first. There is some evidence that...

Look, I'd like to see your project suceed as much as the next guy, but you are approaching it like it is your senior project in college instead of a professional software engineering project. If you don't care what end users need or apply some more rigor to the development process, you'll end...

QUOTE]Quote from Raul641: If you are seriously interested in auditing the robustness or security of the code, you can do so Come on are you serious... if? Your codebase needs to developed within the framework of a software engineering process because of the seriousness potential bugs can...

It is beholden upon both the provider of the libraries and the application itself to ensure the highest quality of code. You guys seem too cavalier about all this. People will potentially be staking large sums of money on the code that you produce. But hey, it's no skin off your back if a...

Wrong. Users will being placing trades with real money. What if your interface hangs due to a bug that you could have discovered using a formal QA process and the user can't exit their position? It can cost a trader a lot of money. It would leave them with no recourse since they are using...

As strictly a programming exercise in Ruby it's not. As professional software development it is, because it's just rehashing something that has already been done, without solving any existing problems, without adding new functionality, without market research as to what the end users need...

Some of you are missing the point. It's not about you and how fast you can develop software. It's about the end user and what problems you are solving or new functionality you are providing them. This project doesn't seem to do either. Therefore, other than a way to gain programming experince...

It's a great programming exercise for you, but it probably never will be useful for traders, because it doesn't add any additional functionality that isn't already available in the Java interface. In fact as others have pointed out, it may be slower

I actually prefrr 4-line break charts, as it doesn't whipsaw or give false breakouts as much as 3-line does,

Exactly. It's fine to try and build up geek points and get some experience in Ruby development with this project, but I would urge most traders to bypass this as just a curiosity for now. If you really wanted to be helpful to the end user, you would work on extending the existing Java API (if...

I understand the point of view from a developers perspective about the framework, but what does this new interface bring to the table for traders? Again, what problems is it solving for traders that the Java interface lacks?

So what problems does having a new Ruby interface solve? Can you articulate what feature set in the Ruby interface makes this an improvement over the Java interface? BTW, if you are doing this to get experience as a Ruby developer and have something to put on your resume, then that's fine.