Learn Web Development for FREE

🧵👇️

Transform your body in next 6 months.

People will charge INR 27,000+ for this course.

I am giving away the entire course for FREE:

Module 1:
Build your Fat Loss Diet Plan

· Step by Step Tutorial
· Length: 26

Module 2:
Learn how to easily track your calories/macros.

· Step by Step Tutorial
· Length: 17

Module 3:
Calculate how many weeks it will take to reach six pack.

. Math behind building six pack
· Length: 12

Module 4:
Learn how to Burn Belly Fat in 3 steps

· Science behind belly fat
· 100% Works
· Length: 15

'Tera mera rishta kya, hindu, hindu,hindutva' is a clear take on 'tera mera rishta kya,la ilaha illallah'. As much as Hindutva hates the monotheistic religions especially Islam, there's a strange wistfulness and subliminal need at display now, to BE that they hate. 1

Charlie Hebdo doesn’t come up as a cautionary tale now but rather 'why cant we be like that'?
Growing up, Hanuman was an adorable deity for us, who swallowed the sun, or who couldn’t figure out what was Sanjeevani booti so he picked up a whole mountain and came back with it. 2

Or he was loyal, admirable and when he cleaved his chest, you saw both Ram and Sita. Now we have a lot of “Angry Hanuman” stickers. Why is a cute childlike God angry? We don’t know. It's a convenient blank space where to paint all the angst of Hindu Khatre mein hain narrative. 3

The other strange thing that has started happening is pictures of Ram appearing sans Sita. “Jai Siya Ram” has become “Jai Shri Ram”. Some people disingenuously explain it as being the same thing - because Shri is a name of Lakshmi. Not really. Siya is an apbhransh of Sita. 4

Shri is a prefix of respect in this case. Hinduism is being militarised. A woman/Sita has no place in it. Even the militaristic Goddess that is Durga has no place in this conception of neo-Hindu divinity, as evidenced by Dilip Mandal wondering where Durga came from. 5

Act of 1871
This is Long but it will end with a BOOM

With no constitutional authority to do so, Congress created a separate form of government for the District of Columbia, a ten-mile square parcel of land (see, Acts of the Forty-first Congress,”

Section 34, Session III, chapters 61 and 62).
The act — passed when the country was weakened and financially depleted in the aftermath of the Civil War — was a strategic move by foreign interests (international bankers) who were intent upon gaining a stranglehold on the coffers

and neck of America.
Congress cut a deal with the international bankers (specifically Rothschilds of London) to incur a DEBT to said bankers. Because the bankers were not about to lend money to a floundering nation without serious stipulations, they devised a way to get their

foot in the door of the United States.
The Act of 1871 formed a corporation called THE UNITED STATES. The corporation, OWNED by foreign interests, moved in and shoved the original Constitution into a dustbin.

With the Act of 1871, the organic Constitution was defaced — in effect vandalized and sabotage — when the title was capitalized and the word “for” was changed to “of” in the title.

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.