BC CULTURE

$ry \u2606 loving ron era$

ry ☆ loving ron era
@trans_frodo 5 years, 9 months ago 571 views

Save to PDF Share See On Twitter

the hobbit + onion headlines: a thread

https://t.co/EHGDX2eHbV

https://t.co/G8reDNoqkV

https://t.co/WHk6SU39Dg

https://t.co/dAZbovbbFP

https://t.co/t1ZTT5NxBe

https://t.co/XHE0c34BkG

https://t.co/gppme3qfYc

https://t.co/eOUpjA099O

https://t.co/bqT2A5U0Lv

https://t.co/cDlrjcwbfu

https://t.co/BgZycmgDq5

https://t.co/YRJq4SAn8i

https://t.co/UyYHTFb5Il

https://t.co/4jOkmlgTU6

More from Culture

Pulp Librarian
@PulpLibrarian

Are you writing a sci-fi or fantasy novel? Are you struggling to choose a title for it?

Well good news! I've just analysed the titles of 1,500 DAW sci-fi and fantasy novels, and I think I've found the secret!

Come with me...

Jeet Heer
@HeerJeet

1. Now that Stan Lee is being eulogized far and wide, it's important to remember how marginal Stan Lee and his collaborators (Jack Kirby and Steve Ditko) were in the 1950s and 1960s.

2. Marvel Comics (before that Atlas) was just a cog in the machine of a bottom pulp publisher run by Martin Goodman, the husband of one of Lee's cousins. It was the lowest of the low in the publishing world.

3. Now Mario Puzo (not yet the author of the Godfather) shared offices with Stan Lee in the 1950s and 1960s. Puzo wrote for garrish men's adventure magazines and, like Lee, dreamed of writing a novel & breaking out. But Puzo looked down on Lee.

4. Flo Steinberg, 1960s secretary at Marvel: "They were always making jokes about us. They'd come in and giggle. mario Puzo would look in and would see us all working on his way to the office and say, 'Work faster, little elves. Christmas is coming.'"

5. When JFK was killed, the whole office of Magazine Management was stunned and quiet. Except Lee. He continued working. "He was still working on the comic books," Puzo said. "Like that was the most important thing in the world."

Sister Outrider
@ClaireShrugged

The best way to honour Toni Morrison is to continue her legacy by celebrating and supporting Black female writers. So here’s a thread of fantastic women whose work you should read.

.@yomiadegoke is one of the most interesting and exciting writers I know. Her commentary is always spot on, and has a way of getting you to think deeply about things we’re encouraged to take for granted. She co-authored Slay in Your Lane with the phenomenal @lizuvie.

.@salenagodden’s poetry nourishes the soul. She’s brilliant at recognising inequalities without ever being defeatist. There is so much joy in her words. And Salena’s autobiography is luminous from start to finish.

.@LawrencePatrice has written some of the most gripping YA fiction going in modern day Britain. Her characters are compelling and full of complications - their stories remind readers of how important compassion is.

I always recommend @JackieKayPoet - not just because she gave a blueprint for life as a Black Scottish lesbian, but because there is so much delight and generosity of spirit in her work. Every word counts. She’s also really funny. Proud that Jackie is our Poet Makar.

Rob Ford
@robfordmancs

One of the authors of the Policy Exchange report on academic free speech thinks it is "ridiculous" to expect him to accurately portray an incident at Cardiff University in his study, both in the reporting and in a question put to a student sample.

This is ridiculous. Students were asked for their views on this example and several others. The study findings and conclusions were about student responses not the substance of each case. Could\u2019ve used hypotheticals. The responses not the cases were the basis of the conclusions.
— Eric Kaufmann (@epkaufm) February 17, 2021

Here is the incident Kaufmann incorporated into his study, as told by a Cardiff professor who was there. As you can see, the incident involved the university intervening to *uphold* free speech principles:

The UK govt\u2019s paper on free speech in Unis (with implications for Wales) is getting a lot of attention.

Worth noting then that an important part of the evidence-base on which it rests relates to (demonstrably false) claims about my own institution
1/https://t.co/buoGE7ocG7
— Richard Wyn Jones (@RWynJones) February 16, 2021

Here is the first mention of the Greer at Cardiff incident in Kaufmann's report. It refers to the "concrete case" of the "no-platforming of Germaine Greer". Any reasonable reader would assume that refers to an incident of no-platforming instead of its opposite.

Here is the next mention of Greer in the report. The text asks whether the University "should have overruled protestors" and "stepped in...and guaranteed Greer the right to speak". Again the strong implication is that this did not happen and Greer was "no platformed".

The authors could easily have added a footnote at this point explaining what actually happened in Cardiff. They did not.

$\U0001d683\U0001d69b\U0001d69e\U0001d697\U0001d690 \U0001d67f\U0001d691\U0001d68a\U0001d697 \U0001f1e8\U0001f1e6$

𝚃𝚛𝚞𝚗𝚐 𝙿𝚑𝚊𝚗 🇨🇦...
@TrungTPhan

1/ Amazon is famous for its writing culture:

• "Mock press releases / FAQs" for new product pitches
• "6-page memos" instead of Powerpoint

Two former Amazon execs wrote a book called "Working Backwards" detailing the philosophy.

Here are some insights 🧵

2/ The "Working Backwards" playbook

Instead of creating a product then finding customers, Amazon asks "What does the customer need?" and works toward the product.

✅Customer need --> Create product
❌Create product --> Find customer

3/ Write a mock press release

To determine if the customer need makes biz sense, employees write a press release:

• What problem is the new product solving
• Why it's better than existing options

To persuade a customer, the document has to be jargon-free and tell a story.

4/ Press release forces big thinking

You don't write a press release for an incremental improvements.

Creating a product worthy of a press release means really solving a customer problem and going after markets with large TAMs.

5/ Include an FAQ in press release

Addressing every potential customer question can help identify hurdles to getting something to market...and also uncover opportunities.

💬 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.

Nicolas
@necolas

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.