11 years on Twitter. The world changed in these 11 years

So I was talking to @gewt about Job: A Comedy of Justice and I came up with a theory that I think explains why Heinlein's late-period work is so kinda-terrible and why I still enjoy it so much

So Heinlein had always been very interesting in the short parts of his novels, like the little snippets inside chapters. He had a very fun writing style, and wrote some fun dialogue with fun characters, right?>
It probably comes from how much of his early stuff was short fiction

And I think what happened with a lot of his longer works is that he'd just start writing fun bits and hope it would end up going somewhere or having a bigger plot by the end. like eventually he'd figure out where this was going, then go back and rewrite it into a cohesive whole

and I'm sure he had editors that'd help this process. No editor would let you publish something as rambly and changing-gears-every-other-chapter as The Number Of The Beast, for example... unless you were God-King Of Science Fiction 1980s Robert Heinlein.

so basically I think what happened is that by the 80s (when he was in his seventies!!) he lost the drive to go back and rewrite and he was too Untouchable for editors to make him.

💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.

दधीचि ऋषि को मनाही थी कि वह अश्विनी कुमारों को किसी भी अवस्था में ब्रह्मविद्या का उपदेश नहीं दें। ये आदेश देवराज इन्द्र का था।वह नहीं चाहते थे कि उनके सिंहासन को प्रत्यक्ष या परोक्ष रुप से कोई भी खतरा हो।मगर जब अश्विनी कुमारों ने सहृदय प्रार्थना की तो महर्षि सहर्ष मान गए।

और उन्होनें ब्रह्मविद्या का ज्ञान अश्विनि कुमारों को दे दिया। गुप्तचरों के माध्यम से जब खबर इन्द्रदेव तक पहुंची तो वे क्रोध में खड़ग ले कर गए और महर्षि दधीचि का सर धड़ से अलग कर दिया।मगर अश्विनी कुमार भी कहां चुप बैठने वाले थे।उन्होने तुरंत एक अश्व का सिर महर्षि के धड़ पे...

...प्रत्यारोपित कर उन्हें जीवित रख लिया।उस दिन के पश्चात महर्षि दधीचि अश्वशिरा भी कहलाए जाने लगे।अब आगे सुनिये की किस प्रकार महर्षि दधीचि का सर काटने वाले इन्द्र कैसे अपनी रक्षा हेतु उनके आगे गिड़गिड़ाए ।

एक बार देवराज इन्द्र अपनी सभा में बैठे थे, तो उन्हे खुद पर अभिमान हो आया।

वे सोचने लगे कि हम तीनों लोकों के स्वामी हैं। ब्राह्मण हमें यज्ञ में आहुति देते हैं और हमारी उपासना करते हैं। फिर हम सामान्य ब्राह्मण बृहस्पति से क्यों डरते हैं ?उनके आने पर क्यों खड़े हो जाते हैं?वे तो हमारी जीविका से पलते हैं। देवर्षि बृहस्पति देवताओं के गुरु थे।

अभिमान के कारण ऋषि बृहस्पति के पधारने पर न तो इन्द्र ही खड़े हुए और न ही अन्य देवों को खड़े होने दिया।देवगुरु बृहस्पति इन्द्र का ये कठोर दुर्व्यवहार देख कर चुप चाप वहां से लौट गए।कुछ देर पश्चात जब देवराज का मद उतरा तो उन्हे अपनी गलती का एहसास हुआ।

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.