moleike

sealed trait Term
case class Const(name: String) extends Term
case class Var(name: String) extends Term
case class Atom(relation: String, terms: Term*)
sealed trait Clause
case class Rule(head: Atom, body: Atom*) extends Clause
case class Fact(atom: Atom) extends Clause
case class Query(name: String, atoms: Atom*) extends Clause

moleike

{-# LANGUAGE DataKinds         #-}
{-# LANGUAGE DeriveGeneric     #-}
{-# LANGUAGE FlexibleContexts  #-}
{-# LANGUAGE LambdaCase        #-}
{-# LANGUAGE NamedFieldPuns    #-}
{-# LANGUAGE OverloadedStrings #-}
{-# LANGUAGE QuasiQuotes       #-}
{-# LANGUAGE RecordWildCards   #-}
{-# LANGUAGE TypeOperators     #-}

moleike

Keybase proof

I hereby claim:

• I am moleike on github.
• I am moleike (https://keybase.io/moleike) on keybase.
• I have a public key whose fingerprint is CDC4 894D F650 5812 3224 B997 C5CD DE66 C45A DD8F

To claim this, I am signing this object:

moleike

import io.finch._
import io.finch.syntax._
import shapeless._
import scala.language.existentials

trait Route {
  private object base extends Endpoint[HNil] {
    def apply(input: Input): Endpoint.Result[HNil] = EndpointResult.NotMatched
  }
  

moleike

Driver:
  -Write the code according to the navigator's specification
  -Listen intently to the navigators instructions
  -Ask questions wherever there is a lack of clarity
  -Offer alternative solutions if you disagree with the navigator
  -Where there is disagreement, defer to the navigator. If their idea fails, get to failure quickly and move on
  -Make sure code is clean
  -Own the computer / keyboard
  -Ignore larger issues and focus on the task at hand
  -Trust the navigator - ultimately the navigator has the final say in what is written

moleike

package main

import (
	"fmt"
	"io"
	"io/ioutil"
	"net"
	"os"
	"strings"

moleike

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

moleike

obj-m += tcp_svr_sample.o
 
all:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
 
clean:
	make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clea

moleike

Understanding the Memory Layout of Linux Executables

Required tools for playing around with memory:

• hexdump
• objdump
• readelf
• xxd
• gcore

moleike

input {
  lumberjack {
    # The port to listen on
    port => 5043

    # The paths to your ssl cert and key
    ssl_certificate => "/etc/pki/tls/certs/logstash-forwarder/logstash-forwarder.crt"
    ssl_key => "/etc/pki/tls/private/logstash-forwarder/logstash-forwarder.key"
    
    # default type, but this will already be set by logstash-forwarder anyways