| # Rubocop git diff'ed files | |
| alias rubostaged="bin/rubocop -a `git diff --name-only --staged | grep '\.rb'`" | |
| alias rubodiff="bin/rubocop -a `git diff --name-only | grep '\.rb'`"" |
| #!/bin/bash | |
| # Clean all exited containers | |
| docker ps -qaf status=exited | xargs docker rm | |
| # Remove all unused images | |
| docker images -f dangling=true -q | xargs docker rmi |
| on is_running(appName) | |
| tell application "System Events" to (name of processes) contains appName | |
| end is_running | |
| set iTunesRunning to is_running("iTunes") | |
| set noMusic to "no music is playing" | |
| set song to noMusic | |
| if iTunesRunning then | |
| set song to run script "tell application \"iTunes\" to if player state is playing then \"now playing: \" & name of current track & \" by \" & artist of current track" |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
| /** | |
| * Deep diff between two object, using lodash | |
| * @param {Object} object Object compared | |
| * @param {Object} base Object to compare with | |
| * @return {Object} Return a new object who represent the diff | |
| */ | |
| function difference(object, base) { | |
| function changes(object, base) { | |
| return _.transform(object, function(result, value, key) { | |
| if (!_.isEqual(value, base[key])) { |
Author of Employee to Entrepreneur
Advisor to companies
"50% of people dissatisfied with work (US, UK, AU)"
Criticism of "building a side hustle": "bringing worst level of work when you get home at 7pm"
prioritizing, automating, outsourcing: allows you to free up time to focus on your strengths and get into flow (!)
analogy of tenacity with learning how to surf: "getting back on the board"
build a healthy relationship with adversity: actively seek out uncomfortable situations
tldr; Storybook is a great tool for creating a style guide that is easy to test and develop.
Storybook is a development environment for UI components. It allows you to browse a component library, view the different states of each component, and interactively develop and test components.
Storybook runs outside of your app. This allows you to develop UI components in isolation, which can improve component reuse, testability, and development speed. You can build quickly without having to worry about application-specific dependencies.
tldr; Gatsby is great if a dev owns the site and it isn’t too large. Next is better for a larger site or if you’re building an app
