#BajajFinance dipped right into the Buy Zone, made low at 5912 and bounced back.

KANIPAKAM VINAYAKA, CHITOOR (AP)
#bharatmandir

Kani means wetland and Pakam means flow of water into wetland.
Kanipakam Vinayaka is swayambhu (self-manifested). The murti is in a well which is always full of water.

Once, there were three brothers. Each one had a handicap- Dumb, Deaf and Blind. They had a small piece of land for livelihood. For their field, they drew water from a well. One day, they found that the well had dried up so one of them started digging in the well.

His tool hit something and blood oozed out. They found a swayambhu murti of Ganesha here.
Villagers started offering coconut water which overflew into a channel. Hence the name Kanipakam.

The murti is still growing in size. At present, we see the knees and the abdomen only. The Kavacham (Armour) offered to Vinayaka 50 years ago doesn’t fit today.
Vinayaka is believed to be the upholder of truth. So people come here and swear before him to prove their innocence.

Saptapadi

The most essential rite (Sanskrit: rītī) of a Hindu marriage ceremony is Saptapadi (English: seven steps, saptapadī). Saptapadi is a Sanskrit term that means "seven steps." The wedded couple walks seven steps after tying the Mangalsutra, which is known as Saptapadi.

The couple legally becomes husband and wife after the seventh step.
Hindu wedding rituals: During Saath Phere, the bride and groom exchange their marital vows while circumambulating (walking around) the sacred fire seven times.

This is because the bride and groom exchange marriage vows and hope for a happy married life together.

1. The first marriage vow, out of seven, is a petition to the Lord for nutrition and nourishment for the Hindu bride and groom.

2. Hindu Bride and Groom: The second marriage promise is for strength in sickness, health, good times, and terrible times.

3. For the Hindu Bride and Groom - The third marriage promise is for the Hindu bride and groom's prosperity.

4. For Hindu Bride and Groom - The fourth pledge is to stand by their families in good times and bad.

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.