| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>Ansi 0 Color</key> | |
| <dict> | |
| <key>Alpha Component</key> | |
| <real>1</real> | |
| <key>Blue Component</key> | |
| <real>0.10618455708026886</real> |
| Root { | |
| raws: { semicolon: false, after: '\n\n' }, | |
| type: 'root', | |
| nodes: | |
| [ Comment { | |
| raws: [Object], | |
| type: 'comment', | |
| parent: [Circular], | |
| source: [Object], | |
| text: 'TACHYONS' }, |
One day a designer visited Master HyperTextCascade, and inquired, “Master, how will my designs be different when I have mastered code?”
Master HyperTextCascade answered, “Before code: identify problem, research, test, ship, iterate, solve problem. After code: identify problem, research, test, ship, iterate, solve problem.”
Several years ago I got curious about how css worked at scale. When I first started out, there weren’t nearly as many learning resources as there are now. CSS zen garden was amazing, at the time it showed how much you could change a design without altering the html.
In the beginning, that’s what people sold me as a feature. By writing css, you could make a change one place and have it propagate everywhere. In principle this sounds pretty good. I’m lazy so I like doing things one time. But eleven years later, my experience on both large and small teams is that this is the most terrifying thing about css.
https://twitter.com/thomasfuchs/status/493790680397803521
In the past few years a lot of very smart people have been thinking more about CSS and this has lead to some fascinating discussions around how to build ‘scalable’ ui and how that relates to CSS. When I first started to think about scalability I naturally started to read every blog post and watch every tech talk I could get
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Tue, 20 Jan 2015 16:48:39 GMT till Wed, 20 Jan 2016 16:48:39 GMT.
Only first 1000 GitHub users according to the count of followers are taken. This is because of limitations of GitHub search. Sorting algo in pseudocode:
githubUsers
.filter(user => user.followers > 539)
| { | |
| "module": "git+https://9gke37d40a7a9f84659e98f386d4ea2fda2a5d86:x-oauth-basic@github.com/org-name/repo.git#71e84fd", | |
| "module2": "git+https://9gke37d40a7a9f9999e98f386d4ea2fda2a5d86:x-oauth-basic@github.com/org-name/repo.git#99h43ae", | |
| "module3": "git+https://9gke37d40a7a9f33759e98f386d4ea2fda2a5d6:x-oauth-basic@github.com/org-name/repo.git#94i53bb" | |
| } | |
In visual perception a color is almost never seen as it really is - as it physically is. THis fact makes color the most relative medium in art.
In order to use color effectively it is necessary to recognize that color deceives continually. To this end, the beginning is not a study of color systems.
What counts here - first and last - is not so-called knowledge of so-called facts, but vision --seeing.
| git diff --name-only --stat @{2.weeks.ago} >> changed.txt && git ls-files >> all.txt && comm -23 all.txt changed.txt >> unchanged.txt |
| { | |
| "averages": { | |
| "specificity": 10.647272727272727, | |
| "ruleSize": 1.1894988066825776 | |
| }, | |
| "size": 72608, | |
| "gzipSize": 12722, | |
| "selectors": [ | |
| { | |
| "selector": "article", |
| Plugin 'gmarik/Vundle.vim' | |
| Plugin 'tpope/vim-fugitive' | |
| Plugin 'sjl/gundo.vim' | |
| Plugin 'kien/ctrlp.vim' | |
| Plugin 'othree/html5.vim' | |
| Plugin 'ag.vim' | |
| Plugin 'SirVer/ultisnips' | |
| Plugin 'honza/vim-snippets' | |
| Plugin 'tpope/vim-bundler.git' | |
| Plugin 'tpope/vim-rails.git' |