190 karma · joined June 26, 2011
Talk to me if you’re interested in learning more about Lookout, or if you need to solve a problem with technology.
Let’s build something.
Write a function that enables the following API...
createOlympian()
.name('Katie Ledecky')
.sport('Swimming')
.country('USA')
.log()
// Katie Ledecky, Swimming, USA
Next, if things are going well, I have the candidate transform a JSON collection response to match some arbitrary requirements using Lodash/Underscore.After that, I focus on the candidate's experience and talk about projects they've worked on, their process and what they're looking for in their next position.
If you're a front-end candidate that's solid at design, visualizations or complex layouts, I'd encourage you to bring your personal laptop and show off some of the work you've done on your own.
There were two primary drivers the led me to adopt Redux.
1) When working with multiple services to build a single view, Backbone models are the wrong abstraction. Redux allows you to work with arbitrary data structures without the need to deal with hooking up events between nested models/collections. It also prevents overfetching or having to resort to nested models when a single endpoint serves multiple views.
2) Managing complex asynchronous flows becomes easier when there's a single source of truth.
The backends for frontends pattern that Netflix and Thoughtworks have written about is another approach to dealing with the multiple services issue, but in reality, it's not an option for every project.
https://www.safaribooksonline.com/library/view/an-introducti...
https://www.safaribooksonline.com/library/view/intermediate-...
If you have specific designs/requirements to work from, it may be easier to build the charts with D3 than trying to shoehorn a stock chart into matching the spec. Behaviors like linking chart interactions to independent components (or vice versa) become easier to implement as well.
If you care less about flexibility, Chartist is a solid contender: https://gionkunz.github.io/chartist-js/
Egghead.io also has some good courses https://egghead.io
It'd be interesting if the payments were structured so that they were made by the hiring company, bringing the developer on with a reduced salary (or not) for the first year... or if they could be taken care of pre-tax. Not sure about the feasibility of those approaches.
Vanilla JS or React, you can't have 1200 images sitting on a web page all at once without optimizing for what the user is actually looking at and interacting with.
function myFunction() {
var a, b, func;
func = function () {
return {
attrA: function (attr) {
a = attr;
return this;
},
attrB: function (attr) {
b = attr;
return this;
},
toString: function () {
console.log([a, b].join(' '));
return this;
}
}
}
return func();
}
This allows us to call myFunction multiple times, set attributes (imagine it were createPerson instead, with a name, age, etc...) and not run into problems with state being shared.I like this question because it covers closures, this, objects and functions. It also doesn't qualify as a brain teaser, IMO.
If it goes well (first scenario), I like to spend the rest of the interview pairing on a task like writing a parse method for a Backbone model that needs to transform a response for a charting library or something like that with Underscore/Lodash.
One time, a candidate started checking emails on his phone during an on-site interview. That candidate wasn't hired.