I woke up this morning really pissed off that I had to write this thread because a senior guy who doesn’t like me very much just happened to write this article about things I was tweeting about and in the process downplayed homophobia and got the story wrong 😡

I’m pissed also at everyone who read that blog entry and walked away thinking, “oh he sounds like a good guy who has been unfairly maligned who should have a space telescope named after him.” Excuse me, what?
Most of you would never been foolish enough in 2021 to say such a thing about a man who sanctioned institutional anti-Black racism but you think that’s an ok message to send to queer people, including Black queer people?
And he’s gonna get away with it too. No matter what I say, that blog entry will keep making the rounds and people will believe it even though it hasn’t been through a formal edit and fact check process.
Next time Hakeem should maybe send me an email rather than write vague, unprofessional personal attacks like: "astrophysicist who propagated unsubstantiated false information as if it were true without performing proper scientific rigor to investigate its veracity"
I should say that I have had Hakeem blocked on twitter for a couple of years and I actually really don’t want to go into why, but the Hitler was a good guy joke at the last NSBP meeting I attended was gross
I want to be clear that I interpret that blog entry as the leader of a professional society and a senior scientist going out of his way to:
- justify historic homophobia
- attack a junior queer Black woman professor for being angry about homophobia because ...he doesn’t like her
Hakeem and I once had a procedural disagreement during an NSBP business meeting in 2011 when I was a first year postdoc and *10 years later* he is writing poorly researched articles that are basically hit pieces on me, and I am fucking tired
Any astronomers who have seen the piece in circulation should speak up with their chest to people who are posting it about both its factual problems and its moral failings

More from Society

This is a piece I've been thinking about for a long time. One of the most dominant policy ideas in Washington is that policy should, always and everywhere, move parents into paid labor. But what if that's wrong?

My reporting here convinced me that there's no large effect in either direction on labor force participation from child allowances. Canada has a bigger one than either Romney or Biden are considering, and more labor force participation among women.

But what if that wasn't true?

Forcing parents into low-wage, often exploitative, jobs by threatening them and their children with poverty may be counted as a success by some policymakers, but it’s a sign of a society that doesn’t value the most essential forms of labor.

The problem is in the very language we use. If I left my job as a New York Times columnist to care for my 2-year-old son, I’d be described as leaving the labor force. But as much as I adore him, there is no doubt I’d be working harder. I wouldn't have stopped working!

I tried to render conservative objections here fairly. I appreciate that @swinshi talked with me, and I'm sorry I couldn't include everything he said. I'll say I believe I used his strongest arguments, not more speculative ones, in the piece.

You May Also Like

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.
A THREAD ON @SarangSood

Decoded his way of analysis/logics for everyone to easily understand.

Have covered:
1. Analysis of volatility, how to foresee/signs.
2. Workbook
3. When to sell options
4. Diff category of days
5. How movement of option prices tell us what will happen

1. Keeps following volatility super closely.

Makes 7-8 different strategies to give him a sense of what's going on.

Whichever gives highest profit he trades in.


2. Theta falls when market moves.
Falls where market is headed towards not on our original position.


3. If you're an options seller then sell only when volatility is dropping, there is a high probability of you making the right trade and getting profit as a result

He believes in a market operator, if market mover sells volatility Sarang Sir joins him.


4. Theta decay vs Fall in vega

Sell when Vega is falling rather than for theta decay. You won't be trapped and higher probability of making profit.