This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# BASIC ALIASES | |
alias ll='ls -ltraFGh' | |
alias rm-secure='rm -RP' | |
alias trash='trash -v' | |
alias hs='history 0 | grep' | |
alias opensh='nano ~/.zshrc' | |
alias newsh='source ~/.zshrc' | |
# Z-SHELL SETUP | |
# SAVE ALL THE HISTORY |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/** | |
* This is a strategy I came up with to write HTTP API Clients in Kotlin. It has a couple of motivations: | |
* 1. Posting public documentation for your REST API is a nice thing to do, but requiring your customers to | |
* pay programmers to implement it is a bit of a bummer. If you write the HTTP API, you are going | |
* to be the proverbial 10x programmer when you write the API client. Your customers will thank you, | |
* especially if 'customers' means 'other programmers in the same organization'. | |
* | |
* 2. API versioning is a thing. Versioning the API Client automagically signals to users that | |
* the API is changing and how they need to adjust *via compilations errors!* |