- intro (read script below)
- Tell me a story about the last time you taught someone something at work. what was the process like? what went well / what was challenging? (This is a warmup softball question. The candidate will be prepared for something like this, and will relax while answering it.)
- Tell me a story about the last thing someone taught you at work. (Looking for: ability to learn, learning strategies.)
- Substitute for #2 for more senior candidates: How do you deal with stress? (Looking for: any thoughtful approach at all.)
- What’s the hard part of [your job]? (Look for reasons why it's hard; what the candidate is doing to learn more about making it easy. Is it technical or do they have the awareness to talk about people things?)
- Tell me a story about a time modularity (or encapsulation) worked out for you. how do you pick where to encapsulate? what’s good about modularity? what’s difficult? (This is the single most important question fo
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette. See also my blog at www.janvsmachine.net.
Keep it simple, stupid. You ain't gonna need it.
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
Moved to Shopify/graphql-design-tutorial
Below is the list of modern JS frameworks and almost frameworks – React, Vue, Angular, Ember and others.
All files were downloaded from https://cdnjs.com and named accordingly.
Output from ls
command is stripped out (irrelevant stuff)
$ ls -lhS
566K Jan 4 22:03 angular2.min.js
This is a list of Ember components that can hopefully inspire your own solution to handle some really common cases. Please let me know of more.
Either copy the aliases from the .gitconfig
or run the commands in add-pr-alias.sh
Easily checkout local copies of pull requests from remotes:
git pr 4
- creates local branchpr/4
from the githubupstream
(if it exists) ororigin
remote and checks it outgit pr 4 someremote
- creates local branchpr/4
fromsomeremote
remote and checks it out
Donut | |
Penguin | |
Stumpy | |
Whicker | |
Shadow | |
Howard | |
Wilshire | |
Darling | |
Disco | |
Jack |