BC TECH
Saved by @zmbnski
John Horton
John Horton
@johnjhorton 3 months, 2 weeks ago 92 views

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
In short, despite Flash skills being expensive to acquire, workers abandoning a skill with no perceived future create a de factor highly elastic supply curve, keeping wages "flat." We show how this is possible with a little toy model, of course.
We also conduct a survey of Flash workers affected by the decline. They confirm many of our stylized facts & give color to the adjustment process. For one, they report being highly-forward looking and market-oriented & deciding what skills to pick up
They also emphasize how critical on-the-job learning is to acquiring new skills. Sadly for us teachers, formal classroom learning gets almost no love
Anyway, lots more in the paper & thanks for reading this far- check it out! https://t.co/w6nLf1tnST Comments, feedback, suggested citations (even to/esp to your own papers) most welcome!

More from Tech

Advertisement
ashkan soltani
ashkan soltani
@ashk4n
BREAKING: @CommonsCMS @DamianCollins just released previously sealed #Six4Three @Facebook documents:

Some random interesting tidbits:

1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition


2) Facebook engineered ways to access user's call history w/o alerting users:

Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.


3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.

4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.

https://t.co/PwiRIL3v9x
TECH
Tom MacWright
Tom MacWright
@tmcw
it's done.

a visual enigma machine simulator: https://t.co/eLE4Sb97HW
TECH

You May Also Like

Guillaume Chaslot
Guillaume Chaslot
@gchaslot
The YouTube algorithm that I helped build in 2011 still recommends the flat earth theory by the *hundreds of millions*. This investigation by @RawStory shows some of the real-life consequences of this badly designed AI.


This spring at SxSW, @SusanWojcicki promised "Wikipedia snippets" on debated videos. But they didn't put them on flat earth videos, and instead @YouTube is promoting merchandising such as "NASA lies - Never Trust a Snake". 2/


A few example of flat earth videos that were promoted by YouTube #today:
https://t.co/TumQiX2tlj 3/

https://t.co/uAORIJ5BYX 4/

https://t.co/yOGZ0pLfHG 5/
TECH
Daddy Files
Daddy Files
@DaddyFiles
This is my son, Sam. He’s 5. And today he learned how shitty and harmful #ToxicMasculinity is. My rage meter is spiking right now so excuse me if this is a little raw but there are some things I want to say about BS #gender norms (a thread)


Sam is my middle child & he’s a terror. A “boy’s boy” as so many (not me) would say. He’s rough and tumble, he’s loud, he’s always dirty, loves trucks, plays sports and knee drops me from the couch. But he also loves a lot of “girl” things.

Sam has a collection of purses because he likes to carry things around. And he also loves to have his nails painted bright colors because he thinks they “look beautiful.” And he’s right – they are beautiful…


So he proudly wore his red nail polish to kindergarten this morning because Sam has absolutely no concept of nail polish only being for girls or reason to think anyone would possibly have a problem with beautiful nails.


But his classmates did have a problem. A big one. Sam was ridiculed for being a boy with nail polish. They called him names and told him to take it off. This lasted the entire day.
Advertisement
Advertisement
Filippo Valsorda
Filippo Valsorda
@FiloSottile
“We don’t negotiate salaries” is a negotiation tactic.

Always. No, your company is not an exception.

A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.

Listen to Aditya


And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.

I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.

You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.

Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]
LIFE
Laurie Voss
Laurie Voss
@seldo
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.
TECH