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
| # fino-time.zsh-theme | |
| # Use with a dark background and 256-color terminal! | |
| # Meant for people with RVM and git. Tested only on OS X 10.7. | |
| # You can set your computer name in the ~/.box-name file if you want. | |
| # Borrowing shamelessly from these oh-my-zsh themes: | |
| # bira | |
| # robbyrussell |
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
| (copy-paste of email sent to [email protected], [email protected]) | |
| Greetings! | |
| I've just read a whitepaper the two of you authored (hope you are still at spotify to receive this email), I accessed it here: https://dl.dropboxusercontent.com/u/1018963/Articles/SpotifyScaling.pdf | |
| I would love to discuss how this has continued to work since 2012 if either of you have any time (I am located in PST, but can be flexible on meeting outside of my normal working hours). If async communication works better for ya'll, no worries! My main two questions are: | |
| - Since 2012, how has the model evolved? Has it proven to continue to be successful after 5 more years of scaling up? | |
| - The paper makes no mention of remote workers. Judging by what it says w.r.t. face-to-face communication and co-location of squads/tribes (and the pictures showing very un-remote-friendly physical task management) my assumption is Spotify does not embrace any remote work (at least not as of 2012). Has this situation changed? If |