PLEASE NOTE: We'd prefer you send your answers to [email protected] rather than post them publicly in another Gist or in comments on this Gist ;-)
Each voter can vote in zero or more referenda. Each referendum has one or more questions, and each question is a yes/no vote. Write the simplest normalized schema to describe this in generic SQL statements or as an entity-relationship diagram. Point out where the indexes would be if you want to quickly know the results of a given referendum question, but you never expect to query a single voter's voting record.
Your client plans to host their web application on AWS. When would you advise (a) deployment in a single availability zone, (b) deployment in multiple availability zones in a single region (c) deployment in multiple regions? What operational difficulty or complexity, if any, is added as you go from (a) to (b) to (c)?
You're working on a cool branch of the foobar project, and your branch contains two commits A and B. The git lineage is:
X -- Y -- Z <-- master
\
A -- B <-- your-cool-branch
You want to contribute the code back to the master foobar repo, but you realize there is a really dumb typo in one of your source code comments in commit A. You'd still like to submit the pull request as two commits A' and B', where A' is the fixed version of A, and B' is the same exact diff as B. How do you rewrite git history to make this happen? Is B' the same hash as B? Why or why not?
What's Module.included
? What is a common (meta-)programming construct in which it is used? Give an example and explain exactly what's going on.
New code was released to multi-tier production environment and now the site is SO slow. But it worked great on the single-server staging environment, which has only half the CPU and half the RAM of the production servers!
Here's the code that's behaving poorly:
class Post < ActiveRecord::Base
def comments
comment_ids = Comment.where("post_id = ?", self.id).map { |c| c.id }
comment_ids.map { |comment_id| Comment.find_by_id(comment_id) }
end
end
What's wrong? And why did it work well (enough) on the staging server?
Obviously the person who wrote this isn't a Rails programmer. How would a Rails programmer have written the code?
In one Unix command, find all of the files in /usr/local
whose contents contain the word "aardvark" (case-insensitive), and list them all in order from most-recently created to least-recently created.
Usage of the "!important" CSS declaration is often frowned upon by front-end developers. What does the "!important" CSS declaration do? Why do front-end developers suggest using it with caution? What are some cases in which it makes sense to use it?
Take a look at the following:
function *foo(x) {
while (x < 4) {
x += yield x;
}
return x;
}
var bar = foo(3);
console.log( bar.next(1) );
console.log( bar.next(1) );
console.log( bar.next(1) );
What is the output of this code snippet, and why does it behave in the way it does?