- People over tools
- Sw over doc
- Collaboration over contract
- Change over plan
- Be restful
- Put view partials in proper resource (table partial, not table body)
- Namespace a lot, use lib a lot, but don't put app (eg AR models) stuff in lib
- Models should not use change itself in callbacks; Use services, strategies, queries, have a clear dependency hirarchy
- Limit the use of validation (defaults?), they are only for UI purposes, (almost) always add relative DB constraints
- DB foreign_keys, unique indexes, null with defaults
- No SQL outside of the model
- Write extra models (or Query objects?) to connect models
- Write non-AR models
This file contains hidden or 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
| # Read File System | |
| # alias ag='ag -C' # -C 5 # Context | |
| alias aglog='ag "\>\>\>"' | |
| alias agdeb='ag binding\.pry app/ lib/ vendor/ config/ spec/ && ag debugger app/javascript/ app/assets/javascripts/' | |
| alias agig="ag --ignore-dir={vendor,vendir,node_modules,cache,tmp,test}" | |
| # alias agit='ag --ignore="*_test\.*"' | |
| alias agl='ag -l' # file only | |
| alias agq='ag -Q' # no regex | |
| alias agw='ag --width=300' | |
| alias bigfiles="find . -type f -printf '%s %p\n' | sort -nr | head -30" |
Currently interested in ReactJS, Node, TypeScript, AI, UX.
This file contains hidden or 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
Show hidden characters
| { | |
| "added_words": | |
| [ | |
| "App", | |
| "refactored", | |
| "refactor", | |
| "api", | |
| "ui", | |
| "async", | |
| "linter", |
This file contains hidden or 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
| # CGI.parse(params) # "checklist_list_ids%5B%5D=10806" | |
| # Gem::Specification.map(&:name).sort | |
| # app.users_path # => "/users" | |
| ::U = User # Etc | |
| def self.helpme | |
| puts <<-TEXT | |
| v # view helpers (eg: content_tag) | |
| exceptions # List of all exceptions |
This file contains hidden or 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
| ## NODE-REINSTALL | |
| #!/bin/bash | |
| # node-reinstall | |
| # credit: http://stackoverflow.com/a/11178106/2083544 | |
| ## program version | |
| VERSION="0.0.17" |
This file contains hidden or 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
| git for-each-ref --sort=-committerdate --format='%(committerdate:short)|%(refname)|%(authorname)' refs/heads refs/remotes | head -n20 | awk -F '|' '{ printf "%s %-70s %s\n", $1, $2, $3 }' |
| title | date | author | tags |
|---|---|---|---|
The Direction Of The Dependency |
2016-02-26 |
Architecture, Dependency Management, Ruby |
When projects grow they become hard to change. One aspect that is not often highlighted is dependency direction. I haven't found much material on the topic, maybe the best ideas came from this talk by Sandi Metz "Less, the path to a better design".
