🧵 NEW: How fair is Britain?

Wealthy families are surprisingly good at hanging onto their riches from generation to generation.

Our bank of mum and dad - one of the most generous in Europe - is making things worse... https://t.co/8PVzDjDw7y" target="_blank">@thetimes

https://t.co/8PVzDjDw7y

[THREAD: HISTORY OF THE HINDU TEMPLE]
1/102
Four hours south of Aswan in Lower Nubia, right by the Nile, is a region dotted with temple complexes built more than 3,000 years ago. Some like the temples of Amada, Derr, and Beit el-Wali go as far back as 1500 BC.

2/102
A little further south, not far from the border with Sudan, is another complex dedicated to Ramses II, Hathor, and Nefertari in the village of Ipsambul, better known locally as Abu Sunbul and internationally as Abu Simbel. These go back to the 13th century BC.

3/102
Djeser-Djeseru, also known as the mortuary temple of Hatshepsut in Upper Egypt also dates to 1400 BC. Over 500 years older is the nearby Mentuhotep II, also a mortuary temple. Both were dedicated to the cult of Amun Ra, besides their respective pharaohs.

4/102
Far older is the Ġgantija complex of Malta. Going as far back as 3600 BC, this one comprises of two temples entirely made of stone and enclosed in a stone wall. From the figures therein, it's understood to be a site of some kind of a fertility cult worship.

5/102
Dating from the same period are the limestone megaliths of Ħaġar Qim and Mnajdra, both said to have once hosted ritualistic sacrifices as part of the same fertility cult worship as found in the Ġgantija complex. Malta has some of the oldest temple complexes in Europe.

HORANADU ANNAPOORNESHWARI, CHIKMAGALUR (KAR)
#bharatmandir

Annapoorneshwari is the Devi of nutrition and food. The literal meaning of Annapoorneshwari is “Feeding one and all”. Anyone who comes here is offered meals and shelter within the premises.
@LostTemple7

Maharshi Agastya is believed to have done pratishtha here.

Once, Shiva and Parvati had an argument. Shiva declared everything in the world including food to be Maya or illusion. To prove him wrong, Devi Parvati disappeared resulting in entire Earth becoming still.

Taking pity, Devi appeared as Annapoorna and relieved everyone.
Another belief is that once Shiva beheaded Brahma and his skull got stuck in Shiva’s hand. He was cursed that till the skull is not full of food or grains, it will remain stuck to his hands.

Shiva went everywhere and asked for food but the skull was never full. He finally came here and Maa Annapoorna filled the skull with grains and reversed Shiva’s curse.

It is believed that who ever visits Devi Annapoorna here will never be without food in their lives.

The Haas / Force India argument is fascinating, and the decision of the stewards may still have consequences. The first key finding is that the stewards ruled Racing Point Force India to be a valid constructor. That means that it builds its own cars.

Haas had argued that the cars had been designed by Force India, but as Haas knows only too well, "outsourcing" is legal. The stewards decided that "there is no regulatory support for the argument that Outsourcing of Listed Parts cannot come from a former or excluded team."

In determining this, the stewards also came to the following conclusion: "In relation to the submission by the Racing Point Force India F1 Team that it is not a new team, the Stewards decide that the Racing Point Force India F1 Team is indeed a new team."

This will have a big knock on effect for Haas in its continued arguments over the rights of RPFI as relates to its eligibility and rights under the complex payments structure. Haas has argued all along that RPFI should be treated as a new team and tread the same path that it did.

TLDR? Haas lost the fight but may have won the war. In having its argument that Racing Point hadn't designed their own car thrown out, they gained clarification that RPFI was a new team.

1/ Here are my notes from @robertwrighter's book - Nonzero: the logic of human destiny. I enjoyed the book very much.

The basic premise of the book is that history has a direction which favors co-operation and non-zero sum games, and that causes an increase in complexity.

2/ Starting from the first replicating molecule which co-operated with an outer layer to form first proto-cell, evolutionary and cultural history is full of examples where two entities come together to survive and progress a lot more than they would have done individually.

3/ This co-operative entity fares much better than two individual entities because of specialization. If two entities are in the same boat - that they win together or lose together - then trust is implicit.

4/ In a non-zero sum game, trust causes entities to focus on what they do best.

For example, eukaryotic cells - the ones animals and plants have - emerged when two proto-cells merged, and one took the role of energy generator (mitochondria), the other specialized in protection.

5/ Some scientists believe that even nucleus in a cell is a result of an early cell merging with another cell.

So M&A is not a recent phenomena, entities have been merging because of common interests ever since life started.

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.