Skip to content

Instantly share code, notes, and snippets.

View seahyc's full-sized avatar
🎯
Focusing

Seah Ying Cong seahyc

🎯
Focusing
View GitHub Profile
@seahyc
seahyc / rancher-slack.js
Last active May 17, 2019 20:40
Listens to Rancher websocket events, and notify through slack webhook when application is upgraded
/*
Setup:
npm install ws
Usage:
Create an API key in Rancher and start up with:
node socket.js address.of.rancher:8080 access_key secret_key project_id
*/
var WebSocket = require('ws');
@seahyc
seahyc / docker-compose.yml
Created February 15, 2017 07:31
docker-compose.yml for rancher-server and rancher-nginx
version: '3'
services:
rancher-server:
image: rancher/server
container_name: rancher-server
ports:
- "8080:8080"
volumes:
- /root/mysql:/var/lib/mysql
- /root/mysql-log:/var/log/mysql
@seahyc
seahyc / technical_test.md
Last active October 10, 2023 19:35
Glints Technical Test

1. Factorials

You are given an integer N. Print the factorial of N, as defined below.

N! = N * (N-1) * (N-2) * ... * 3 * 2 * 1

Input

@seahyc
seahyc / engineering_manager.md
Last active March 7, 2018 16:31
Engineering Manager Job Description

Engineering Manager

Our north star metric for this year is 1000 placements made through our platform. As such, the roles we individually play might shift fluidly based on the situation. That being said, here are some of the gaps that we need filled at our stage:

  • Trainining, guiding and coaching junior developers
  • Improve our workflow and processes to improve site reliability, and to close feedback loop from customers
  • ~30% of the time is in code review or hands-on code on bigger, more difficult projects
  • Guide team on technical and architectural decisions
  • Ensure timely shipping of end-user value whilst maintaining reliability and quality of the product
@seahyc
seahyc / frontend_interview.md
Last active March 22, 2018 03:54
Customization and Configuration

Customization and Configuration

Glints whitelabels its platfrom to several client. These are sites that share the same codebase as the main glints site, but has its custom styles and at times components.

An example is IE Singapore and JOS, vs main Glints.

How would you design our architecture to support flexible and extensible configuration/customization for whitelabel sites?

@seahyc
seahyc / hours.csv
Last active February 5, 2020 04:16
Extended restaurant list after deduplicating extension list
Kushi Tsuru Mon-Sun 11:30 am - 9 pm
Osakaya Restaurant Mon-Thu, Sun 11:30 am - 9 pm / Fri-Sat 11:30 am - 9:30 pm
The Stinking Rose Mon-Thu, Sun 11:30 am - 10 pm / Fri-Sat 11:30 am - 11 pm
McCormick & Kuleto's Mon-Thu, Sun 11:30 am - 10 pm / Fri-Sat 11:30 am - 11 pm
Mifune Restaurant Mon-Sun 11 am - 10 pm
The Cheesecake Factory Mon-Thu 11 am - 11 pm / Fri-Sat 11 am - 12:30 am / Sun 10 am - 11 pm
New Delhi Indian Restaurant Mon-Sat 11:30 am - 10 pm / Sun 5:30 pm - 10 pm
Iroha Restaurant Mon-Thu, Sun 11:30 am - 9:30 pm / Fri-Sat 11:30 am - 10 pm
Rose Pistola Mon-Thu 11:30 am - 10 pm / Fri-Sun 11:30 am - 11 pm
Alioto's Restaurant Mon-Sun 11 am - 11 pm
@seahyc
seahyc / software_engineer_coding_test.md
Last active June 12, 2020 07:32
Enlarged sample input size for hdb task

General Brief

There are 2 questions in the assessment, which you can answer in any language. For each test, please commit your code to a private repository on GitHub, with a README.md on how to run it. When you’re done, simply add seahyc and yjwong as collaborators to your private repository.

There's no time limit, but do time yourself for every question beginning from the time you start reading it till your final local commit, and let me know how long you took for each question in the README. We recommend that you set aside 1.5 hours for each task in the test.

You can take in the input either via command-line arguments, or simply assume that it's assigned at the top of your script. Either way, let us know how to inject an input. We'll adapt our test cases accordingly. Very importantly, we trust you to write your solutions independent of any external help.

Task 1

@seahyc
seahyc / data_team_coding_test.md
Last active November 21, 2019 18:29
Added general brief

General Brief

There are 3 questions in this part.

There's no time limit, but do time yourself for every question beginning from the time you start reading it till your final local commit, and let us know how long you took for each question in your README.

Task 1: The Trigram

Given a large chunk of text, write a program that can identify the most frequently occurring trigram in it. If there are multiple trigrams with the same frequency, then print the one which occurs first. Assume that trigrams are groups of three consecutive words in the same sentence which are separated by nothing but a single space and are case insensitive.

@seahyc
seahyc / data_team_take_home.md
Last active October 29, 2019 06:13
Added general brief

General Brief

This assignment has 2 parts to it. You may attempt the bonus section, which will definitely add to the final score if well-executed upon.

Main Task

Implement this part of the task with Apache Spark using Docker. Given a set of keywords, find the top k most similar documents among a set of N documents from the dataset - (click this link to download all-the-news.zip), using Apache Spark and Docker. Your Apache Spark setup should consist of more than 1 slave.

Your submission:

@seahyc
seahyc / backend_development_test.md
Last active April 1, 2020 07:13
Added in deployment instructions

Finding the Next Unicorn

You work at a venture capital firm, HardBank, which is hell-bent on finding the next unicorn startup to invest in. They appointed you to build a tool to search through all the startups for patterns of success and failure. If it works, they’ll also open it up for public access.

Your general partner, Mahayoshi Sonny, dumped you a json file of company profiles (https://ufile.io/gzpnra8msk1s902) that his data team has assiduously compiled over many years.

He’d like you to build an API server, with documentation and a backing relational database that will allow any client to navigate through that sea of data easily, and intuitively. The front-end team will later use that documentation to build the front-end clients.

The choice of the language and server framework is up to your discretion, you just need to explain your decision later. As for database, you can pick any so long as it is a relational database. In the dataset, each company has many attributes, but for this projec