KrauseStefan

git config --global format.pretty '%h %aN - %Cgreen%s %Creset: %Cred%ar %C(reset)%C(auto)%d%C(reset)'

KrauseStefan

# List certificates
certutil -d $HOME/.pki/nssdb -L

# Add certificate
# Tested with base64 incoded cert
# Source: https://grox.net/sysadm/unix/chrome.import_ca_cert
certutil -d sql:$HOME/.pki/nssdb -A -n '<PrettyName>' -i <path to cert>.crt -t TCP,TCP,TCP

KrauseStefan

PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\w\[\033[00m\] [\[\033[01;34m\]$(__git_ps1 "%s")\[\033[00m\]]$ '

KrauseStefan

If the order of lines is not important##

Sort lines alphabetically, if they aren't already, and perform these steps:
_{(based on this related question: https://stackoverflow.com/q/1573361/3258851)}

1. Control+F

2. Toggle "Replace mode"

3. Toggle "Use Regular Expression" (the icon with the .* symbol)

KrauseStefan

#!/bin/bash
#set -x 

# Shows you the largest objects in your repo's pack file.
# Written for osx.
#
# @see http://stubbisms.wordpress.com/2009/07/10/git-script-to-show-largest-pack-objects-and-trim-your-waist-line/
# @author Antony Stubbs

KrauseStefan

[System.IO.FileStream]::new("C:\file-path\filename.txt", [System.IO.FileMode]::Open) 

KrauseStefan

gradle.taskGraph.afterTask { task ->
    StringBuffer taskInfo = new StringBuffer()
    taskInfo << """"-------------
name:$task.name group:$task.group : $task.description
conv:$task.convention.plugins
inputs:
"""
    task.inputs.files.each{ it ->
        taskInfo << "${it.absolutePath}\n"
    }

KrauseStefan

If you're using [kotlin-dsl] in a multi-project manner, you may want to define all the dependencies in one place. You can put the files into buildSrc, define dependencies in a compat way like this:

extra.deps {
    "kt"("stdlib-jre7")
    "auto" {
        "common"("com.google.auto:auto-common:0.8")
        "service"("com.google.auto.service:auto-service:1.0-rc3")
    }
 "gson"("com.google.code.gson:gson:2.8.0")

KrauseStefan

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

KrauseStefan

function zip ($zipFilePath, $targetDir) {
  # load Ionic.Zip.dll 
  [System.Reflection.Assembly]::LoadFrom(path\to\Ionic.Zip.dll)
  $encoding = [System.Text.Encoding]::GetEncoding("shift_jis") # 日本語のファイルを扱うために必要
  $zipfile =  new-object Ionic.Zip.ZipFile($encoding)

  $zipfile.AddDirectory($targetDir)

  if (!(test-path (split-path $zipFilePath -parent))) {
    mkdir (split-path $zipFilePath -parent)