The timing is no coincidence, as the MDN docs team was part of those layoffs. It would be a cruel act to layoff the MDN team while also trying to improve the perception of MDN's value.
This is a great reminder of a lot of tools, and the closing thoughts are excellent:
"Still, JavaScript is the most brittle of all front-end web technologies. An important skill of a front-end developer is to know when not to solve a problem with client-side JavaScript. It is always more robust to solve a problem further down in the stack."
The overwhelming majority of these points are useful, and the exact thing that "engineering culture" Twitter has been excelling at for a while now. It wasn't always easy to find people supporting people at every stage of their career, but there are several accounts to follow to do just that.
The "one page ahead in the manual" quote is a great example of this. It's hard to remember when you didn't know everything you know today -- so think about yesterday, or last week, some smaller time slice. What did you learn yesterday that somebody on your team may not know? Operating at that layer and sharing knowledge freely shows you're a friendly resource and shows that you're honest about your journey. It attracts other people who are slightly above or below that level, who can share and multiply what you're learning.
(And it has a great byproduct of teaching you where the egos sit at your company.)
This is presented in the linked document with the following context-specific gotchas:
> Unfortunately, this method only works when the source object contains serializable value types and does not have any circular references. An example of a non-serializable value type is the Date object - it is printed in a non ISO-standard format and cannot be parsed back to its original value :(.
Useful background, thank you. Am I alone in thinking the response from Palantir looks like more feedback than one would have expected from the average corp? It makes jamiebuilds' reply seem more provocative than it otherwise would have, but I praise their conviction to their morals.
Edit for vague closing sentence: I'm praising jamiebuilds' moral conviction.
I think I see what the OP meant, here are relevant excerpts from the article. New API access:
> Beginning today, anyone who wants access to Twitter’s APIs should apply for a developer account using the new developer portal at developer.twitter.com.
Existing API keyholders:
> Eventually, all developers with existing access to our APIs will be required to complete a developer account application in order to maintain their apps.
I don't think I understand how the rules will affect that, won't the 300 per 3 hours limit on tweets still only affect the "app" a user generated their keys for?