[1/4] Ok this is really funny, check this out.
I was in the process of booking a flight via @OneTravel. Trying to make me book ASAP, they claimed: "38 people are looking at this flight".
Whoa, 38 is a lot, I have to hurry up. But first I have to check how they came up with 38 >>

Technical Analysis Masterclass- Part 2

'Entering the trade'

Entering a trade without ascertaining a certain things is gambling.

In this masterclass we will learn the pre-requisites to enter a trade.

DON'T ENTER A TRADE WITHOUT DETERMINNG THE FOLLOWING.

Please share.

We understand what reward to risk (popularly called risk to reward) is.
It will be denoted by R:R.

We will also try to bust a few myths about R:R and how to avoid losing trades.

Before entering a trade, you need to determine 3 things.

1. Entry trigger
2. Stop loss
3. Target

1. Entry trigger = Reasons for entering a trade. There could be multiple reasons or a single reason for entry.

Generally a set of reasons AKA confluence is a higher probability trade and a generally a safer entry.

Example of an entry trigger.

2. Stop Loss.

The price in the opposite direction of the trade where the trade is exited, at a loss.

At this level, the reason for the entry becomes invalidated according to TA and the price can then move in the opposite direction, probabilistically.

3. Target is the possible price level that the asset might touch based on previous trends or confluence AND where a possible reversal could occur.

Target is the next path of least resistance from where the price might reverse.

We will always ONLY use TA to determine all 3.

Thread 🧵explaining #ROE & #ROCE and its use in #FundamentalAnalysis

(Must read for #FA learners)

🙏Like & RT to spread learning with all 🙏

Views Welcome 👉 @dmuthuk @Vivek_Investor @datta_arvind @caniravkaria @FI_InvestIndia @AdityaD_Shah

#FundamentalAnalysis #StockMarket

1⃣

Return on Equity (#ROE) and Return on Capital Employed (#ROCE) are two important Financial Ratios used in #FundamentalAnalysis of Stocks.

#StockMarket #Investing

2⃣

Return on Equity (ROE) is the ratio of Net Income (Net Profit) of a company and it’s Total Equity (Shareholder's Equity).

Here - Shareholders Equity = Share Capital + Reserves & Surplus.

#StockMarket #Investing #FundamentalAnalysis

3⃣

#ROE is a measure of how much net profit a company is making for every rupee invested by its shareholders in the company.

It can be said that higher the ROE, better it is for the equity shareholders. It tells shareholders about how effectively their money is being used.

4⃣

However, you should not trust high ROE blindly. Biggest drawbacks or weaknesses of ROE is that it completely ignores debt.

Hence for companies having high levels of debt, ROE will give a higher but misleading value & therefore we need to look at #ROCE along with #ROE.

Guruvayur Sri Krishna & Coconut with Horns.
#Krishnaleela
#Bhakthi
🕉
We’ve all grown up listening to stories of Shri Krishna. This one is a famous story of Shri Krishna in Guruvayur Temple, also called Dakshina Dwaraka.

There lived a villager who planted coconut saplings and had promised that he would offer the 'first coconut' from each of his coconut trees to "Guruvayurappan". When the trees started to yield coconuts, he collected the first coconut from all the trees in a sack 👇

and set forth to Guruvayur.

On the way he was stopped by a robber who asked all the items in the sack. The villager told the robber that the coconuts in the sack belonged to Guruvayurappan and so he was unable to hand it over.
@SriramKannan77 @Jayalko1

The robber with anger asked the villager "Is Guruvaurappan's coconut any different? Does it have horns ?".
Saying so the robber pulled the sack forcefully out of the villager's hand, and coconuts came out..👇

To their astonishment each and every coconut in the sack had horns! Even today, the coconut with horns are displayed in the temple for devotees to see.

Below Picture is not original, as we cannot take photos inside temple.
Hare Krishna
Guruvayurappa
🕉🕉🕉🕉🕉
Shubham

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.