So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.

Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.

What happens when a skill you have becomes obsolete? No, this isn't a R vs. Stata thread---it's a thread about a working paper w/ @sonnytambe!
https://t.co/w6nLf1tnST

The skill we look at is Adobe Flash, which @apple decided to no longer support back in 2010, which in turn caused demand/interest to plummet, as measured on @StackOverflow and in online labor markets, one of which is our empirical context

Despite the big fall-off in Flash jobs posted, very little else appeared to change in the market for Flash skills: wages for Flash jobs didn't fall, jobs didn't become easier to fill & openings weren't inundated with out-of-work Flash programmers

What happened was that (a) new entrants stopped specializing in Flash and (b) at least some existing Flash specialists started moving to other skills. In short, the demand shock quickly became a supply shock

At the level of the individual Flash worker, using a matched sample, we find (a) no fall-off in their wages, (b) some decline on-platform hours-worked. The most-focused on Flash workers had substantial increases in application intensity and a movement towards new skills

I’m quoted in this, which does about as good a job overviewing the topic as a New York Times profile can be expected to.

Major oversights in it as I see.

First, It does not acknowledge the fact that Yudkowsky is, at heart, a complete crank. This remains, to my mind, crucial to understanding the rationalist community’s influence on the world: they’re sci-fi writers being mistaken for scientists.

You can’t really understand the harmful effects of SSC until you realize that it’s part of a larger movement of bullshit artists serving as cult leaders to the techbros.

Second, and more importantly, it never really explains the harm that’s being done by Scott Siskind and his followers. It comes close, noting that “SJWs” were the only group not welcome in SSC, but it doesn’t capture the harm of that because it doesn’t unpack the term.

What is meant in practice when “SJWs” aren’t welcome in a space is that marginalized people speaking of the harm they experience are silenced.

That’s it. That’s the meaning.

Setting up Git/GitHub to work with R/RStudio can be challenging.

Here's a thread to walk you through the process step by step.

This thread also lives in blog post form. #rstats

Preamble: the best overall resource, and one I rely on extensively, is Happy Git with R by @JennyBryan and @jimhester_.

If you have additional questions about Git/GitHub + R/RStudio, this should be your first

The first step to set things up is to install Git.

Chapter 6 of Happy Git with R lays out the process for Mac, Windows, and Linux users.

I’m on a Mac so Git came pre-installed on my computer. I was able to verify that I had Git installed using the terminal in RStudio.

The next step is to configure Git.

This is covered in Chapter 7 of Happy Git with R , though I show what I believe to be a slightly easier process using the edit_git_config() function from the {usethis} package.