Skip to content

Instantly share code, notes, and snippets.

View leite08's full-sized avatar

Rafael Leite leite08

View GitHub Profile
@leite08
leite08 / untilfail.sh
Created March 23, 2023 21:25
Shell script to run a command until it fails
#!/bin/bash
count=0
while "$@"; do (( count++ )); done && echo "It failed on the $count iteration"
@leite08
leite08 / post-merge
Created February 27, 2023 16:55
Husky git hook to notify about changes on files/folders upon merge
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"
# Place this on ./husky and make sure the file is executable (chmod 770 post-merge)
changed() {
git diff --name-only HEAD@{1} HEAD | grep "$1" > /dev/null 2>&1
}
echo "Checking updates on <file-type> files..."
@leite08
leite08 / clean_code.md
Created March 5, 2022 23:07 — forked from wojteklu/clean_code.md
Summary of 'Clean code' by Robert C. Martin

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