When short term gets confusing, zoom out to long term charts. #Nifty

#CNXIT still must do a minimum 52K++ (to complete its move from Oct 2001 low) & therefore any dip between 26K-29K is a good buy zone. Also has mid-line support right there (previously resistance).

Remember: Just because an idea is old doesn't mean it's good.

Knowing whether old ideas are more likely to be good requires understanding whether conditions have changed in important ways.

Horse archery was an amazing method of warfare for over a thousand years...then people invented guns, and suddenly this great idea that had stood the test of time became obsolete.

Then again, when underlying conditions don't change much, tried-and-true approaches are probably better.

"Learning the lessons of history" usually just means assuming ergodicity and stationarity in an informal time-series model...

(end)

KANAKA DURGAMMA, VIJAYWADA (AP)
#bharatmandir

Ma Kanakadurgeswari is the supreme Goddess of Andhra Pradesh, seated atop the Indrakilaparvatha at Vijayawada.
This area is called Bezawada as Shiva made a bejjam (hole) in the rocks so that Krishna river could flow freely.

Once, a Rishi Indra Keela prayed to Devi and asked her to reside on his head forever. Devi told him to wait in the form of a mountain in the holy plains of River Krishna.
Later, when Devi killed all demons, she settled on Keeladri as Mahishasura Mardini and fulfilled his wish.

In this place, Arjuna performed penance and fought with Shiva, who had appeared in the guise of Kiratha to win Pasupathastra, the most powerful weapon. So this place is also called phalguna theertha and Vijaywada on account of Arjun’s victory.

Adi Sankaracharya visited this shrine and worshipped the Devi. He installed SRICHAKRAM at the feet of Sri Kanaka Durga.

Adjacent to the Kanakadurga shrine is the shrine of the divine consort-Sri Malleswara Swamy on the Indrakeeladri.

So, I want to talk about how sexual harassment and fair pay are linked at Google (and beyond), because I think that's an angle that isn't being highlighted enough in the coverage of these walk-outs. I'm going to frame it largely around my personal experience there. Thread.

When I was sexually harassed by the director of the area I was working in, I was afraid to report it because I was worried that "getting him in trouble" would result in the subtle retaliation of missed leadership opportunities.

I wanted to continue working on the team I was on, because I'd gained a lot of very deep knowledge and expertise in that area, as well as reputation and camaraderie with the other folks working in that area. I didn't want to make the situation more "difficult."

To get promoted at Google, several need to happen: 1. you need opportunities for ownership and leadership above your current level (basically, opportunities to show you're working at the next level you're trying to get promoted to). The work you're "assigned" has a big impact.

2. You need glowing reviews from peers, *at or particularly above the level you're hoping to get promoted to.* Basically, you need people a lot more senior than you to say you're doing awesome work.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.