nickmarden

/tmp/ruby-build.20220713212425.612.srFiOO /ruby-build
HTTP/1.1 200 OK
Content-Type: binary/octet-stream
Content-Length: 9864061
Connection: keep-alive
Date: Wed, 13 Jul 2022 20:13:01 GMT
Last-Modified: Wed, 06 Jul 2022 01:24:22 GMT
ETag: "90d47d61531f00ea75500354ecf05f3a-2"
Accept-Ranges: bytes
Server: AmazonS3

nickmarden

Fetch this api endpoint See this guide for details about the api.

Display the returned data in whatever format you want. Each post should also display the name of the user and his/her email.

Include:

• a search box to filter out articles by username or title
• a control to order alphabetically by username or title

Use functional components, even better if you use TS. Your code should be readable and maintainable.

nickmarden

PLEASE NOTE: Do not publicly post your answers on this Gist, please forward them to your recruiting contact instead ;-)

1. Voting

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. In what way does the nature of the application affect your design judgment about privacy, and what effect would that have on normalization considerations?

2. Rewriting history with git

You've getting ready to submit a pull request to the coolapp repo. You branch contains two commits: M, followed by N. The lineage is this:

nickmarden

PLEASE NOTE: Do not publicly post your answers on this Gist, please forward them to your recruiting contact instead ;-)

1. Voting

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. In what way does the nature of the application affect your design judgment about privacy, and what effect would that have on normalization considerations?

2. Rewriting history with git

You've getting ready to submit a pull request to the coolapp repo. You branch contains two commits: M, followed by N. The lineage is this:

nickmarden

PLEASE NOTE: Do not publicly post your answers on this Gist, please forward them to your recruiting contact instead ;-)

1. Voting

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. In what way does the nature of the application affect your design judgment about privacy, and what effect would that have on normalization considerations?

2. Rewriting history with git

You've getting ready to submit a pull request to the coolapp repo. You branch contains two commits: M, followed by N. The lineage is this:

nickmarden

PLEASE NOTE: Do not publicly post your answers on this Gist, please forward them to your recruiting contact instead ;-)

1. Voting

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. In what way does the nature of the application affect your design judgment about privacy, and what effect would that have on normalization considerations?

2. Rewriting history with git

You've getting ready to submit a pull request to the coolapp repo. You branch contains two commits: M, followed by N. The lineage is this:

nickmarden

Enterprise Data Warehouse Engineer Skills Test

The following is a series of questions related to skills that we commonly use in our enterprise data warehouse (EDW).

This is not a timed or monitored test, and you may use any print or online resources you would like to assist you in your work.

Please submit your answers in the form of text, markdown, or other lightweight data formats. Please indicate clearly which parts of your response correspond to which question. If your answers span multiple files, please attach them as a zip file.

1. HBase Denormalization with Consistency

nickmarden

#!/usr/bin/perl -w
use strict;

my $ROWS  = 10;
my $COLS  = 5;
my $MAX   = 12;

print "\n\n\n\n";

my $q = { };

nickmarden

#!/bin/bash

ZONE=$1; shift
MASTER=$1; shift

usage() {
  echo "Usage: $0 ZONE MASTER EXPECTED_A [EXPECTED_A ...]"
  exit 1
}

nickmarden

#!/bin/bash -x

ES_HOME=/usr/share/elasticsearch
ES_CLASSPATH=$ES_CLASSPATH:$ES_HOME/lib/*:$ES_HOME/lib/sigar/*
ES_HEAP_SIZE=1024m

nohup java \
  -server \
  -Djava.net.preferIPv4Stack=true \
  -Des.config=__HOME__/elasticsearch/elasticsearch.yml \