ktzar

Front-End Take-Home Challenge – Insurance Claims Form

Welcome to the Utility Warehouse Front-End Take-Home Challenge! 💜,🚀

We’re thrilled you're interested in joining our Insurance team — where we help protect what matters most to our customers.

This take-home exercise is simple and short on purpose, as it's just meant to be a foundation for us to work on together during the technical assessment call, and also give you a taste of the kind of work we do. It’s not just about writing code, but also something you’d be happy to discuss with your teammates.

---

ktzar

Commands to open Tmux

# Start new session
tmux
# List sessions
tmux ls
# Attach to a session
tmux a -t sess_num
# Rename a session

ktzar

#!/bin/bash
BITRATE=64
OUTDIR="."
if [ "$1" != "" ]; then
    BITRATE=$1
fi
if [ "$2" != "" ]; then
    OUTDIR=$2
fi

ktzar

From https://blog.thimbleweedpark.com/zero_bugs Don't underestimate the fans. I found quite a lot of them, I think. How many percents would you say those are? Those are present in most versions of the game:

• The storekeeper closes the door AFTER he walks to the counter. (all versions except EGA)
• The line "The basic theory is fine." of the Fettucini Brothers is skipped due to a script error.
• Smirk's cigar's smoke positioning is off.
• Guybrush occasionally refuses to burn the cereals, even after the journey to Monkey Island and vice versa. It is possible to get stuck here if you didn't bring anything else to burn.
• The Piranha poodles freeze briefly before eating the meat.
• Ghost key cloning by repeatedly using the compass on it while in Lechuck's room.
• Storekeeper walks through mid-air when shortening the first open safe cutscene early.

ktzar

<style>
body {
        font-size: 90px;
        text-align: center;
        color: white;
}
</style>
<div id="result"></div>
<script>
window.onload = function () {

ktzar

Why Most Unit Testing is Waste

By James O Coplien from http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf

1.1 Into Modern Times

Unit testing was a staple of the FORTRAN days, when a function was a function and was sometimes worthy of functional testing. Computers computed, and functions and procedures represented units of computation. In those days the dominant design process composed complex external functionality from smaller chunks, which in turn orchestrated yet smaller chunks, and so on down to the level of well-understood primitives. Each layer supported the layers above it. You actually stood a good chance that you could trace the functionality of the things at the bottom, called functions and procedures, to the requirements that gave rise to them out at the human interface. There was hope that a good designer could understand a given function’s business purpose. And it was possible, at least in well-structured code, to reason about the calling tree. You could mentally simulate

ktzar

int sensorValue = 0;
int outputValue = 0;
int previousValue = 0;
const int threshold = 30;
const int analogInPin = A0;

void setup() {
  // initialise serial:
  Serial.begin(9600);
}

ktzar

import serial, time, os
ser = serial.Serial('/dev/ttyACM0', 9600)
while 1:
    time.sleep(0.05)
    try:
        line = ser.readline().strip()
        value = int(line) * 10
        command = 'echo "{0}" > /sys/class/backlight/intel_backlight/brightness'.format(value)
        os.system(command)
        print(command)