unflores

unflores

module Compliance
  module IdentityVerification
    class TestingWebhookSubdomain
      def initialize(stage, env, host)
        @stage = stage
        @host = host
        @env = env
      end

      def value

unflores

 git st | tail --lines=+2| awk -F ' ' '{print $2}'|xargs sed -i 's/\r//g'

unflores

import React from 'react'

class Dots extends React.Component {
  constructor(props) {
    super(props)
    this.state = {
      dots: '',
      timerID: null,
    }
  }

unflores

start "" "C:\Users\unflores\Documents\utilities\putty.exe" -load "dev"

unflores

var Thing = require('./thing');

console.log('Include thing from another file');
console.log(Thing.thing, ":thing in included");

unflores

sudo mount -t vboxsf shared_dev /home/ubuntu/shared_dev/

unflores

sudo tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' -i lo

unflores

# http://docs.rubygems.org/read/chapter/11
--- 
gem: --no-ri --no-rdoc
benchmark: false
verbose: true
update_sources: true
sources: 
- http://gems.rubyforge.org/
- http://rubygems.org/
backtrace: true

unflores

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:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions