#Hdfc
Very interestingly poised to make it's "iii"rd of 3rd wave, "Holding 2740-50".
Confirmation - moving past "2812"

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.

🎉🎉 PHP 7.3 is here!

Here are the things I'm excited about.

🚂 Trailing commas in function/method calls!

This will certainly be a required styling choice for me. Same delightful benefits of trailing comma in multi-line PHP arrays, and JavaScript objects.

🧵 Less disgusting heredoc syntax!

Inlining heredoc strings in any way right now is grrrosssss. Now we get sensible capabilities. Everything that was wrong with it is now fixed!

(Ignore the bad syntax highlighting)

☠️ Finally, not-so-silent json_decode error detection!

This really sucked before, now it just sucks a bit less (who wants to pass a 4th param and pass 2 default params first? (helper function anybody?)

📜 Not horrible functions for getting the first and last item (or key) from an array!

Before you either strung a bunch of functions together or messed with internal array pointers. This is a much-needed improvement.

On December 25 Mr Pool retweeted August 16 message about the Phoenix and that the worst was still on the horizon to come. 1/*

Maybe now we can assume that November 3 message meant "FUD" nor "FUN". Putting the word in capital letters seems to indicate the aspect the word fud has in our space, FUD. 2/*

Brad started it on December 22 (1/3 posts (Don't say? Sure) = 13 = Plan B). 3/*

And immediately the SEC followed dropping the bomb (1.3 billions (Don't say? Sure) = 13 = Plan B). 4/*

FUD materializes, Bitstamp is one of the first that haltes XRP trading and so on. 5/*

THE BATTLE OF TALIKOTA and the destruction of Vijaynagar (Hampi)
26 January 1565

A tale of valor, deception and decimation.

A grim reminder that if we fail to protect our heritage, it will eventually crumble under the onslaught of "forces of anarchy".
(Elaborate thread)

This decisive battle was fought between the Vijayanagara empire and the Deccan sultanates resulting in a rout of Vijayanagara and ending the last major medieval era Hindu kingdom in south India.(1)

The seeds of 1565 encounter were sown more than 250 years earlier when the forces of the Delhi Sultanate, during the time of Alauddin Khilji and later Md Bin Tughlaq swept through southern India in an expansion spree.(2)

By middle of the 14th century, facing rebellions, Tughlaq withdrew to Delhi, leaving behind 2 empires, Bahmani, which ruled the Deccan from Kalaburagi, and Vijayanagara, which ruled most south India with its capital at Vijayanagar.(3)

The Raichur Doab, between the Krishna and Tungabhadra rivers, existed as a natural boundary between these two kingdoms, with wars often breaking out over control of this territory.(4)