I will remember this upmove in bank nifty on 30th Nov ( Tuesday ) in my life.
@_GauravVashisth
@ITRADE191

How you can filter stocks for Intraday trades - 🧵

As a kid, we would do homework before school the next day - you have to do homework here too. A specific sector performs on a particular day and studying things a day before will help you spot that particular sector. (1/11)

To prepare for the next trading day, you got to check the Index charts of all sectors. You got to keep an eye on a specific Index if you see a few factors:

- If any Index closed exactly at the resistance, you can get a trade on either side on the next day. (2/11)

- If it gave a rejection candle at resistance.

- If any Index closed exactly at support, you can get a trade on either side the following day.

- If there was a bullish signal at the support.

- If any Index gave a breakout or breakdown and then gave a good closing. (3/11)

- If any Index has taken support at 50 or 200 EMA.

Once you spot the Index, look at all the stocks in that particular Index. Pick at least 3-4 stocks from that Index and add them to your watchlist for the next day. It's ideal to check both higher and lower timeframes. (4/11)

What you should do next day? (When I am unable to check Indices and stocks a day before, I sometimes directly start with this process.)

- Start with checking the top gainers/losers list. I observe market from 9:15 to 9:45am to check the sectors performing well on that day.(5/11)

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.

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.