#JSWsteel if the momentum works out, this one could hit 1160 / 1200 levels from here. Lets see. Just my study and I could go wrong as well. First targets on this one is 990 levels.

Just my study, no reco

Singing the Blues:
Taking Down an Insider Threat

"I had all of the advantages. I was already inside the network. No one suspected me. But they found my hack, kicked me off the network...

...and physically hunted me down."

Many pentests start from the outside, wanting to see how the perimeter might be breached.

This pentest started from the inside. My client wanted to assume they had already been breached, and, if breached, how far could an attacker go.

Could they stop me once I was inside?

So they snuck me in. Disguised me as a new employee. Gave me a work computer, an ID badge, an account in their system... hell, I even had a cubicle w/my assumed name on it.

The only person who knew who I really was was their CISO. Everyone else thought I was Jeremy in Marketing.

During most of the first morning, I completed onboarding, made introductions, and completed menial tasks.

But I had to act quick. I only had a week onsite. I had to hack their network while not raising suspicion.

So I set about it.

You have to understand... most "Internal Pentests" are straight forward. The hard part is breaching the network, but once you're inside, it's a target rich environment. End of Life computers, default passwords, everyone a Local Administrator...

Some people really benefit from hearing advice that everyone knows, for the same reason we keep schools open despite every subject in them having been taught before.

In that spirit, here's some quick Things Many People Find Too Obvious To Have Told You Already.

Your idea is not valuable, at all. All value is in the execution. You think you are an exception; you are not. You should not insist on an NDA to talk about it; nobody serious will engage in contract review over an idea, and this will mark you as clueless.

Technologists tend to severely underestimate the difficulty and expense of creating software, especially at companies which do not have fully staffed industry leading engineering teams ("because software is so easy there, amirite guys?")

Charge more. Charge more still. Go on.

The press is a lossy and biased compression of events in the actual world, and is singularly consumed with its own rituals, status games, and incentives. The news necessarily fails to capture almost everything which happened yesterday. What it says is important usually isn't.

Companies find it incredibly hard to reliably staff positions with hard-working generalists who operate autonomously and have high risk tolerances. This is not the modal employee, including at places which are justifiably proud of the skill/diligence/etc of their employees.

5 star RSI Strategy by @VishalMalkan

Unconventional approach of 60-40 RSI and range shift concept.

According to him,
whenever the market is bearish,
it won’t be able to cross 60,
and whenever in a bullish trend,
it won’t be able to cross 40.

Like & Retweet for Maximum Reach.

So, instead of the 70-30 Relative Strength Index,
we will use the 60-40 range for the RSI indicator for this strategy.

When the
Monthly and Weekly RSI>60,
& when the RSI takes support at 40 in the daily chart,
it may bounce back and most probably it will not go below 40.

If a bullish candle is formed at the 40 RSI level,
the prices may bounce back, and one can enter the stock.

The stoploss can be placed at the low of that bullish candlestick,
and the target can be the 60 RSI level.

When the
Monthly and Weekly RSI<40,
& when the RSI takes resistance at 60 in the daily chart,
it may bounce back and most probably it will not go above 60

If a bearish candle is formed at the 60 RSI level,
the prices may bounce back from there, & 1 can enter the stock 4 shorting

The stoploss can be placed at the high of that bearish candlestick, and the target can be the 40 RSI levels.

#banknifty

This range shift concept can be applied in any timeframe,
whether intraday, daily,weekly, etc.

THREAD

I get asked for writing tips a lot. Of all the ones I’ve given, here are a few of the ones that seem to hold true and remain somewhat universal or at least mostly unobjectionable:

#amwriting #writingtips

1. If you are a fast writer (i.e., if you compose first drafts very quickly) then you absolutely must become a slow editor. Much of what I call “writing” is really, for me, editing.

2. If you don’t read you cannot write a lot or well. Sure, maybe you can read like a maniac for a decade and then read less after that, but without some large volume of intake, there will never be a meaningful output.

2.1 I sometimes say that I feel like writing without reading is like trying to run a marathan on a cracker. And sadly I see many students struggling to write when they have simply never read enough to fuel that demand of the task at hand.

3. All writing is writing if one decides to treat it that way. If one takes some degree of intentional will when sending emails, posting on social media and writing notes and marginalia, then all of that can count as meaningful daily writing.

THE BATTLE OF SARAIGHAT (1671)

Lachit Borphukan's humiliation of Aurangzeb.

The battle of Saraighat was a naval engagement fought on the Brahmaputra river near Saraighat between the M0ghul empire and Ahom kingdom in 1671.

Guts, resolve and glory!

(Elaborate thread)

Koch was a state situated between the dominions of M0ghuls and Ahoms. For Ahoms, it was a buffer state for keeping M0ghul territorial expansions at bay.(1)

Times changed when the ruler of the Koch kingdom, Nara Narayana passed away in 1587 resulting in Koch being divided into 2. Western Koch was ruled by his son Lakshmi Narayan and the eastern Koch by his nephew, Raghudev.(2)

Lakshmi Narayan formed an alliance with M0ghuls after which he attacked Parikshit, son of Raghudev, in 1602. Parikshit Narayan was defeated while his brother Bali Narayan took refuge in the Ahom Kingdom.(3)

The M0ghuls used it as a pretext to invade Ahom kingdom. The first battle between them took place in 1615 leading to a series of engagements in which both sides had their shares of ups and downs resulting in a stalemate.(4)