Spotting a trend

Quote from logan04x:

I understand that the question I asked was vague and not an easy one to answer. I think it's best for me to stick on to advice on stockcharts.com and build on that as I learn more. Do you guys have any recommendations for books/websites that I should be looking at? I know it must be a FAQ for this site.

Thanks.

To deal with modelling and design, it is best to use logic and consistant heurisitcs.

You start of defing a boundary is senseless. The relation of excessive points in 1. was a cardinal error. To trade to make money you need to do regional analysis. Granted a line determine a boundary but the boundary has to have a purpose that is productive in terms of a goal.

In trading making money is the goal and boundaries tell you when you are approaching a change of conditions. Here in ET, there is no low lying fruit to pick.

If you want to begin at the beginning, the horizontal line is the place. this is where the boundary for sentiment is assessed.

Also, you may want to focus on letting go of an up/down orientation. The orientation in markets is left/right, where dominant moves are from right to left and non dominant moves are from left to right.

The form of display you are using for the market you are interested in is fairly sparse with repect to market data collection and record keeping. This keep you at a definite disadvantage relative to most al other traders.

There are a lot of what ifs in decision making to become a trader. Why not set up a map of the trading space and break it up into the regions that explain to you the status of the market's opportunities (offers) for making money?
 
Quote from spacelord:

It's amusing hearing the cargo cult professor speak about logic.

His magical system couched in logical sounding rhetoric is the prime example of what not to do and how not to think.

Ah, if it isn't the self promoting Trade Fade Creator himself back for another round of catch-me-Baron-&-ban-me-again multialias marketsurfer.

Hey Davie, you get to go propagate with yourself.
 
Quote from jack hershey:

See attached for a first look at annotating using geometry and linear relationships. It is all easily codable and very productive for making money continually.

NB There is a typo on the illustration "satest" should be "fastest". sorry.

Thanks for the post. I see the point you are trying to make from both of your posts.

I actually used stricter huristics to find the lines. It would have found most of the lines you showed if I had eased down the heuristics. .

It's nice to see people commenting, so keep them coming. I'm enjoying spending my weekends on this stuff :). Thanks.
 
Quote from gasman:

Jack Hershey has a tax lien against him for unpaid taxes to the tune of $82,000 that was filed in 2006. If you go to Maricopa County's recorder web site (http://recorder.maricopa.gov/recdocdata/) and type into the Recording Number fields, the following number: 2006 1575958 and click "search" you will be able to see the recorded document.

A background investigation also found that he has no real assets (in terms of real-estate) and does not sit on the board of any company... in fact he is broke and in debt... evidence also shows that Jack has a few failed marriages behind him where he has left monies owed in the split ups. He currently resides in a very modest house owned by his latest partner and lives off her income.

This man has never made a cent trading, that much is obvious.

I'm new here and don't hang around a lot, but I wonder how someone with as few posts as you knows so much about Jack Hershey? I'm confused with some of the posts going around here :confused:.

Can anyone give me some background here?
 
Neat tool you have, looks like a fun thing to work on.

I can tell exactly where you are in the software dev phase, lol I do the same thing. Get an idea of what you want, and jump in and start coding! Seriously, I do same thing all the time. It's a fun way to code, especially if you don't have a boss breathing down your neck asking for shippables.

You've got about 75% of what you want, but the last 25% remains elusive because you're not precisely sure what it's supposed to do when it's done.

Now is the time when you need to step back and play the roll of Project Manager. Pretend it works perfectly (you do NOT need to know exactly what "perfectly" means right now) and you want to explain to your mom what it does. Or the guy working at the lunch counter. Or your bus driver. You have 30 seconds before they yawn and change the subject.

Be as exacting as you can, while still making it understandable to a layperson, in no more than 30 seconds. Write that down, and you have your product spec. Now go finish up!
 
Quote from jack hershey:

See attached for a first look at annotating using geometry and linear relationships. It is all easily codable and very productive for making money continually.

NB There is a typo on the illustration "satest" should be "fastest". sorry.
Jack I enjoy your work....:)
attachment.php
 

Attachments

Quote from logan04x:

I'm new here and don't hang around a lot, but I wonder how someone with as few posts as you knows so much about Jack Hershey? I'm confused with some of the posts going around here :confused:.

Can anyone give me some background here?

Just understand there are a handful of miscreants that stalk posters or have been repeatedly banned on this site.
Learn to think for yourself around here and look that the posts that are obviously from those "mental giants" as a simple and short term distraction and click on their name, and then click to put them on ignore.
 
Quote from SomeYoungGuy:

Neat tool you have, looks like a fun thing to work on.

I can tell exactly where you are in the software dev phase, lol I do the same thing. Get an idea of what you want, and jump in and start coding! Seriously, I do same thing all the time. It's a fun way to code, especially if you don't have a boss breathing down your neck asking for shippables.

You've got about 75% of what you want, but the last 25% remains elusive because you're not precisely sure what it's supposed to do when it's done.

Now is the time when you need to step back and play the roll of Project Manager. Pretend it works perfectly (you do NOT need to know exactly what "perfectly" means right now) and you want to explain to your mom what it does. Or the guy working at the lunch counter. Or your bus driver. You have 30 seconds before they yawn and change the subject.

Be as exacting as you can, while still making it understandable to a layperson, in no more than 30 seconds. Write that down, and you have your product spec. Now go finish up!

Yup, you are right. I'm aiming to build one pattern recognition classs every week and in about 4 months I will have enough stuff to integrate into with a nicer GUI and all. So far it has been alright. Let's see if it turns to be anything useful.
 
Sounds good.

Quote from logan04x:

Yup, you are right. I'm aiming to build one pattern recognition classs every week and in about 4 months I will have enough stuff to integrate into with a nicer GUI and all. So far it has been alright. Let's see if it turns to be anything useful.
 
Back
Top