Genovo

    #!/bin/bash
    set -euo pipefail
    IFS=$'\n\t'

Genovo

#!/usr/bin/python3
#swaSearch.py
#Southwest Air Fare Searcher
#
#
#Default Aiports:
departureAirportCode = "LAX"
arrivalAirportCode = "SJC"
#departureDate=

Genovo

const unary = (fn) =>
fn.length === 1
? fn
: function (something) {
return fn.call(this, something)
}

['1', '2', '3'].map(unary(parseInt))
//=> [1, 2, 3]

Genovo

#!/bin/bash
#puck.sh


# A DNS propagation checker. Fetches in many DNS servers around
# the world for IPs assigned to a given domain.
#
# Author: José Lopes de Oliveira Júnior <http://joselop.es>
#
#

Genovo

const callerMap = {};

function getCaller(error) {
    if (error && error.stack) {
        const lines = error.stack.split('\n');
        if (lines.length > 2) {
            let match = lines[2].match(/at ([a-zA-Z\-_$.]+) (.*)/);
            if (match) {
                return {
                    name: match[1].replace(/^Proxy\./, ''),

Genovo

Folder Structure

Motivations

• Clear feature ownership
• Module usage predictibility (refactoring, maintainence, you know what's shared, what's not, prevents accidental regressions, avoids huge directories of not-actually-reusable modules, etc)

Genovo

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions