- Kalyn Nakano: http://kalynnakano.com
- Tim Van Damme (Dropbox): http://maxvoltar.com
- Allison House: http://allisonhouse.co
- Max Schoening (Heroku, CloudApp): https://twitter.com/mschoening
- Mike Bostock: http://bost.ocks.org/mike
- Jan Dvořák (Apiary): http://www.jdvorak.eu
- Adam Morse (Salesforce): http://mrmrs.cc
- Zeke Sikelianos (Heroku): http://zeke.sikelianos.com
- Julie Ann Horvath (Github): http://julieannhorvath.com
- Alice Lee: http://byalicelee.com
# Begin Custom Bash Prompt | |
green=$(tput setaf 2) | |
blue=$(tput setaf 4) | |
yellow=$(tput setaf 3) | |
bold=$(tput bold) | |
red=$(tput setaf 1) | |
reset=$(tput sgr0) | |
source ~/.git-completion.sh |
Notifications should be:
- Timely
- Relevant
- Actionable
- Tuneable
- coco doughnuts
- voodoo doughnuts
- pip's doughnuts
- blue star doughnuts
- annie's donut shop
- doe donuts
- tonallis donut shop
- donut byte lab
- delicious donuts
These are the languages, frameworks, and tools I'm using in my day-to-day workflow, listed in no particular order. Items that make me go "Oh yeah!" or are my primary tools are marked in bold.
My end-to-end process is front-loaded with research, sketches, whiteboarding, and figuring out a product spec with everyone that's involved in a project. My philosophy is: Design is not solely about deliverables; it's about understanding. It's not about a particular tool or language; it's about communication. It's not about pixels; it's about providing capability. I don't spend a lot of time in any particular application at first. The hardest thing to do well is figuring out what it is you want to design.
- Mission Chinese
- CREAM
- Burma Superstar
- Ice Cream Parlor
- Shanghai Dumpling House
- Homeroom
Best Dishes
- Gnocchi in Monterey @ K&Ps anniversary restaurant (name?).
- Pan-seared / pan-fried local white fish (type?) with wasabi cream sauce in Kauai.
Best Wines
- Patrick's Pinot Noir that he opened while we were in the pool.
- Ben's red he opened around the table in Geneva.
Replace this with a one or two line description of what this PR is intended to do. If it's a new feature, say what it does. If it's a fix for something, say what it fixes (link to an issue if available).
This <adds>/<fixes>/<removes>
:
- Adds something.
- Fixes something.
- Refactors something.
- Nixes something.
What's left:
- Task.