Ruby Norah

i do pedicure for a living but I work from home

[Ruby Norah @RubyNoraheu4u]

Almost skipped this trader’s free market insights. Glad I didn’t.

One of his breakdowns helped me catch a mistake before it got expensive—and completely rethink my approach.

He shares everything for free here 👇
https://t.co/nEWSuJsu8M

[Ruby Norah @RubyNoraheu4u]

@Invest_Brandon I started reviewing assumptions before reviewing the target price. That made it easier to start with the reasoning behind the number.
@aldo1467293

[Ruby Norah @RubyNoraheu4u]

@LeaderInvests A useful detail in my process has been checking whether a news item referred to a new development.
@Mobpy00

[Ruby Norah @RubyNoraheu4u]

@SeffafNet I keep learning from noting the delay between deciding and acting.
@Alexisxwelder

[Ruby Norah @RubyNoraheu4u]

@wallstengine My journal works better for me with one extra step: rewriting confusing checklist wording after the session.
@Desta712748

[Ruby Norah @RubyNoraheu4u]

@GlobalMktObserv One habit that helped: recording whether a retest actually occurred.
@Mwizerwajeancl5

[Ruby Norah @RubyNoraheu4u]

@MartiniGuyYT I spend a bit more time replacing vague strength labels with specific observations now, and the reviews are clearer.
@MadhaaDoni

[Ruby Norah @RubyNoraheu4u]

@Lukasz_on_GPW One adjustment in how I review trades: asking what would surprise me in the other direction.
@maullt1zvc

[Ruby Norah @RubyNoraheu4u]

@CryptosR_Us One thing I now take seriously is sharing the reasoning before revealing the outcome in a review.
@Obamatgga

[Ruby Norah @RubyNoraheu4u]

@cdntradegrljenn I started with one question: how could I make the written criteria easier to interpret? Keeping an example beside each setup definition helped.
@nindongtong

[Ruby Norah @RubyNoraheu4u]

@GVRCALLS One thing my reviews taught me was to spend time recording the time remaining until a scheduled release.
@syahmiemjr

[Ruby Norah @RubyNoraheu4u]

@siyahsancakx The less exciting part of my process: logging failed breaks beside successful ones. Still useful.
@donhenryfrancis

[Ruby Norah @RubyNoraheu4u]

@turc35 I wanted to remember why I stopped using them, so I started archiving abandoned methods with a brief explanation.
@caaacaaa276714

[Ruby Norah @RubyNoraheu4u]

@MarioNawfal For me, tracking time spent on ideas that never triggered made the review more useful.
@apake1539

[Ruby Norah @RubyNoraheu4u]

@Remzztrades The useful change for me was comparing percentage moves over matching periods.
@yayoomi_

[Ruby Norah @RubyNoraheu4u]

@CryptoTweets Recording the volume response I expected but did not see has earned a place in my routine.

[Ruby Norah @RubyNoraheu4u]

@enzoinsidee The habit behind some of my clearest reviews is labeling the source of each price level.

[Ruby Norah @RubyNoraheu4u]

@conorfkenny One small adjustment I stuck with was noting when expected follow-through never appeared.

[Ruby Norah @RubyNoraheu4u]

@TraderDivergent One reason I value writing what I expected the data to change in my setup: it helps me connect the number to the actual plan.

[Ruby Norah @RubyNoraheu4u]

@tbros6868 I began reviewing one recurring issue across different outcomes to give my later reviews a better reference.

[Ruby Norah @RubyNoraheu4u]

@hkuppy @judahrhodie @SchrodingersAlt @BisonInsights I stayed consistent about reviewing two interpretations without choosing a winner immediately to learn from the difference in reasoning.