pnevares
pnevares on Hacker News
Can we get an edit to add (2019) to the title?
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."
Also, maybe the title here should include (2017)?
> Published on December 21, 2017.
The answer is part of the first link in the article (37 hours).
I was going to guess "maybe GitHub or Valve" before seeing this, now it's definitely GitHub.
Posted by
pnevares on Friday February 01, 2019 @12:21AM
from the youtube.com dept.
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.)
There are four PRs in the linked repo, all merged, it's probably an acceptable route to contribute.
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 :(.
That's my error, thanks for the correction.
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.
What are we supposed to be seeing in your second screenshot? I just see an array of DMs, what's being filtered?
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?
The line about Napster references, and later directly quotes, a section from the complaint PDF (page 6, section 16).
The blog post refers to "RCA" three times and "RSA" once, and doesn't seem to define either acronym after reading it once.
Also this?
> And once you fail a build, then every team member in your team has to do deployments and go through the deployment checklist.
Sounds like there's a piece of context missing from the section before it. You have to do the checklist to deploy, and if you fail once, then every member of your team has to do the checklist as well?
You were misled by the slide image interrupting the flow of the text:
So, I build this JavaScript framework at Google. It is used by Photos, Sites, Plus, Drive, Play, the search engine, all these sites. Some of them are pretty large, you might have used a few of them.
[Slide]
This Javascript framework is not open source.
I think it at least partially correlates with knowing what the new role is worth, financially, to you and to the employer. Nobody's going to disclose what the current executive in that role makes but once you get to that level you're prepared to ballpark it. And prepared to know what it would take for you to accept it.
It's always easy to try to make assumptions based on data, but it's just as easy to take away the wrong idea. Do prospective executives negotiate because they're used to negotiation, or because companies are prepared to negotiate salaries for those roles?
I never even considered the second interpretation, which now seems even more appropriate than the first.
I only hope the original author is aware and supportive of the meta-sentiment of the re-upload/re-whitemark response.
I hold out hope that Today in Tabs will be back from its hiatus one day. Got in on it very late but my wife and I loved it.