| # By Pete Warden, @petewarden | |
| # To use this, open ~/.bashrc in your editor of choice, | |
| # and place these settings at the end. | |
| # Based on https://unix.stackexchange.com/a/48113 and | |
| # https://blog.sanctum.geek.nz/better-bash-history/ | |
| # Ignore both duplicate commands, and those that start with a space. | |
| HISTCONTROL=ignoreboth | |
| # Append to the history file, don't overwrite it. |
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette. See also my blog at www.janvsmachine.net.
Keep it simple, stupid. You ain't gonna need it.
See the instructions in README.md for how to run the code.
When developing a feature, you should start by scoping out a spec, developing tests against that spec and writing code against the tests. Working with others to review the spec before starting development is encouraged.
| #!/usr/bin/env PYTHONIOENCODING=utf-8 python | |
| # encoding: utf-8 | |
| """Git pre-commit hook which lints Python, JavaScript, SASS and CSS""" | |
| from __future__ import absolute_import, print_function, unicode_literals | |
| import os | |
| import subprocess | |
| import sys |
| #!/usr/bin/env python | |
| """ | |
| ===================================== | |
| PEP 20 (The Zen of Python) by example | |
| ===================================== | |
| Usage: %prog | |
| :Author: Hunter Blanks, hblanks@artifex.org / hblanks@monetate.com |