#PLEIADIAN COLLECTIVE

1. Friends Of The Great Planet!

We Gather With You In These Moments To Unveil All Darkness Hidden And Shine Light Brighter Than Ever! As You Observe The Lies Declared To Be Truth, You Will Begin To Notice That Truth Cannot Be Hidden!

#தினம்_ஒரு_திருவாசகம்
தொல்லை இரும்பிறவிச் சூழும் தளை நீக்கி
அல்லல் அறுத்து ஆனந்தம் ஆக்கியதே – எல்லை
மருவா நெறியளிக்கும் வாதவூர் எங்கோன்
திருவாசகம் என்னும் தேன்

பொருள்:
1.எப்போது ஆரம்பித்தது என அறியப்படமுடியாத தொலை காலமாக (தொல்லை)

2. இருந்து வரும் (இரும்)

3.பிறவிப் பயணத்திலே ஆழ்த்துகின்ற (பிறவி சூழும்)

4.அறியாமையாகிய இடரை (தளை)

5.அகற்றி (நீக்கி),

6.அதன் விளைவால் சுகதுக்கமெனும் துயரங்கள் விலக (அல்லல் அறுத்து),

7.முழுநிறைவாய்த் தன்னுளே இறைவனை உணர்த்துவதே (ஆனந்த மாக்கியதே),

8.பிறந்து இறக்கும் காலவெளிகளில் (எல்லை)

9.பிணைக்காமல் (மருவா)

10.காக்கும் மெய்யறிவினைத் தருகின்ற (நெறியளிக்கும்),

11.என் தலைவனான மாணிக்க வாசகரின் (வாதவூரெங்கோன்)

12.திருவாசகம் எனும் தேன் (திருவா சகமென்னுந் தேன்)

முதல்வரி: பிறவி என்பது முன்வினை விதையால் முளைப்பதோர் பெருமரம். அந்த ‘முன்வினை’ எங்கு ஆரம்பித்தது எனச் சொல்ல இயலாது. ஆனால் ‘அறியாமை’ ஒன்றே ஆசைக்கும்,, அச்சத்துக்கும் காரணம் என்பதால், அவையே வினைகளை விளைவிப்பன என்பதால், தொடர்ந்து வரும் பிறவிகளுக்கு, ‘அறியாமையே’ காரணம்

அறியாமைக்கு ஆரம்பம் கிடையாது. நமக்கு ஒரு பொருளைப் பற்றிய அறிவு எப்போதிருந்து இல்லை? அதைச் சொல்ல முடியாது. அதனாலேதான் முதலடியில், ஆரம்பமில்லாத அஞ்ஞானத்தை பிறவிகளுக்குக் காரணமாகச் சொல்லியது. ஆனால் அறியாமை, அறிவின் எழுச்சியால், அப்போதே முடிந்து விடும்.

If u are looking to enter a scrip just before the breakout
what would u look for?
How would u identify scrips just before breakout?

Here are a few pointers
Carefully understand the them and use at ur own discretion
(All comments r compiled from a question i posed)

1/23

Price is testing the same resistance repeatedly since long.
But now in recent times it's forming multiple candles near the same resistance with low volume.
Observe it and see for opposite move.
As soon as u get a positive candle, get in to it.

2/23

1. Volume buildup (vol > when resistance point created) along with, increase in OI, increase in delivery % on HTF
2. On LTF, price stalling around breakout area for at least 1-2hr.
3. No major events.

3/23

Stock reaching breakout LVL with HL-HH
Contraction of price and volume near it especially near 20 days ma.
If there is any breach of the latest HL it should be followed by a bullish candle with good volume.
Left side of the chart has a rally with a very steep slope of ma.

4/23

Number of wide range green bars with high volumes.
If stock is at its ATH then it adds more conviction bcz there wont b supply after that point

Consolidation below the resistance, volume of the candles & strong bullish candle closing at near highs just below the resistance

5/23

IMPORTANCE OF SATYA NARAYAN KATHA AND ITS ORIGIN.

We all have heard and read the Satyanarayan katha. But none of us dont know the original stories that Shatanand or Sadhu or Kalavati must have heard. Also, as a habit we hear or read this katha

but dont know the proper way it should be conducted.

We find its mention in Skanda puraan(Reva khand) and Bhavishya Puraan(Pratisarg parva).
Both Bhagwatam and Gita call Bhagwan Narayan as Satv or Truth. So Satyanarayan denotes this name as the one which is Truth incarnate.

The story began in Naimisharanya when Vyasji asked Sutji about a way to eliminate all the sorrows and fulfill all the desires and about who is the devta who can grant these at the same time.

So Suutji first prayed to Bhagwan Satyanarayan who is no one else but Vishnu ji.

Then he remembered all his avatars.After that he narrated the story of Narad. Once while visiting Mrityulok, Naradji was pained to see the sufferings of People around. He was deeply moved by these sufferings and wanted to know the means by which we could rid ourselves from these.

So he went to Vishnu ji and after paying his respects stood in front of him. Naradji narrated the purpose of his visit.

So Bhagwan Vishnu said to him that in Satyug and Tretayug, Bhagwan eliminates sorrow in Vishnuswarup. In Dwapar he assumes different forms to help people.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.