yakup

alias.co checkout
alias.st status
alias.ec config --global -e
alias.br branch -vv
alias.gr grep -i
alias.ls !git branch -r && git br
alias.up !git pull --rebase --prune $@ && git submodule update --init --recursive
alias.cob checkout origin/HEAD -b
alias.rn !f(){ git branch -m ${1}; };f
alias.task !f(){ git checkout -b t${1}/${2}/${3} origin/HEAD && git status; };f

yakup

ln -s /Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl /usr/local/bin/subl

yakup

const puppeteer = require('puppeteer');
const { defineSupportCode } = require('cucumber')

defineSupportCode(({ Before, Given, When, Then }) => {
  Before({ timeout: 60 * 1000 }, async function testCase() {
    this.browser = await puppeteer.launch()
  })

  Given('I am on google with puppeteer', { timeout: 60 * 1000 }, async function testCase() {
    this.page = await this.browser.newPage()

yakup

# uses xpath to check for a form element based on the label,
#   instead of using a css selector w/ label_for
# name should be the complete name in the html page.
#  meaning Title: and not Title

# find the label that is name.  Get the "for" of the label
# uses the for to check for the input with that as an id

Then /^I should see a "([^\"]*)" for "([^\"]*)"$/ do |type, name|
  case type

yakup

# some aliases
alias ll='ls -alF'
alias la='ls -A'
alias eb="sudo nano ~/.bash_profile && source ~/.bash_profile"
#docker aliases
alias d='docker'
alias dc='docker-compose'
alias dnax="docker rm $(docker ps -aq)"
#git aliases
alias g='git'

yakup

git update-index --assume-unchanged [path]

This works on even commited files

from http://source.kohlerville.com/2009/02/untrack-files-in-git/

yakup

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

yakup

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

yakup

package no.vegvesen.kjoretoy.registrering.register.web;

import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
import javax.persistence.Table;

import java.util.List;
import java.util.stream.Collectors;

import org.springframework.beans.factory.InitializingBean;

yakup

package com.baeldung.restassured.authentication;

import static io.restassured.RestAssured.get;
import static io.restassured.RestAssured.given;
import static org.hamcrest.Matchers.hasKey;

import org.junit.jupiter.api.Test;
import org.springframework.http.HttpStatus;

/**