zahid

Recently, I've been wanting to get more involved with open source, or more accurately, start actually contributing to it. My initial idea was to build a tool that could be quickly cloned via git and used as a base setup for someone who doesn't know how to use Vagrant. This was initially something I called angry-hobo, it worked for a little while, but was a great mess. It didn't work quite right in my opinion.

Here's a list of things that needed improvement:

• angry-hobo cloned a scaffold vs generated a scaffold
• angry-hobo left .git artifacts after cloning which required to be cleaned
• angry-hobo included the Chef cookbooks in the repo, which I later opted against

zahid

# To build this image: 
#   docker build -t app .
#
# To run this image as a container: 
#   docker run --name app --rm -it app

FROM node:6

RUN npm install --global pm2

zahid

User stories

• Continuous integration
  • build image when code is updated
  • deploy image to server
  • restart application
• Make font easier to read
• Put GA so I can see what's happening
• 100 more facts
• 100 more background images

zahid

Description

Build an API with NodeJS with a great, small framework.

This is the NodeJS application pattern.

Quickstart

1. Install dependencies using npm install

zahid

version: '2'

services:

  drools-wb:
    container_name: drools-wb
    image: jboss/drools-workbench-showcase:6.4.0.Final
    ports:
      - 8001:8001
      - 18080:8080

zahid

// TODO: turn this into a "three guys walk into a bar" joke....


/*
You have a list of things you need process, items. In our case, times in seconds.

Use "processItemAsynchronously(timeInMilliseconds)" on each item in "items", while processing the items one at a time.

Each item completes in random time, asynchronously.

zahid

// TODO: turn this into a "three guys walk into a bar" joke....


/*
You have a list of things you need process, items. In our case, times in seconds.

Use "processItemAsynchronously(timeInMilliseconds)" on each item in "items", while processing the items one at a time.

Each item completes in random time, asynchronously.

zahid

( IFS=:;   
for p in $PATH; do       
  ls "$p" | egrep -x '.{2}' ; 
done; )

zahid

/* This is my implementation of the problem regarding replacing the element in the row and column of each instance of a 7 with 7s. I did this without allocating extra memory by just keeping track of the rows and columns that needed to be 'sevenified' and I did it in the end in one pass, therefore not having to rewrite 7s over and over again. My efficiency for sevenify's element reassignment, at the worst case, is O(m+n) or O((m+n) + (m*n)) if you include the cycles to create the locations hash. 

I would test this by checking that: 
  - clone works properly (I tested to check for deep copying)

  - test fillRow (and fillColumn) work on a single row (and column) with no 7s present
  - test fillRow (and fillColumn) work on a single row (and column) with one 7 present
  - test fillRow (and fillColumn) work on a single row (and column) with all elements set to 7

  zahid mahir