mkdir ~/Screenshots
defaults write com.apple.screencapture location ~/Screenshots
| https://stackoverflow.com/questions/29914052/how-to-git-rebase-a-branch-with-the-onto-command/29916361#29916361 | |
| git rebase --onto <newparent> <oldparent> | |
| // Most frequent usage, after base branch is squashed and merged into main | |
| git rebase --onto main [SHA before first commit on your branch] |
This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette.
Keep it simple, stupid. You ain't gonna need it.
| componentDidUpdate(prevProps) { | |
| console.log('Rrow update diff:'); | |
| const now = Object.entries(this.props); | |
| const added = now.filter(([key, val]) => { | |
| if (prevProps[key] === undefined) return true; | |
| if (prevProps[key] !== val) { | |
| console.log(`${key} | |
| - ${JSON.stringify(val)} |
| /** | |
| * Labels Gmail email threads | |
| */ | |
| function labelGithubEmails() { | |
| /** | |
| * Gmail label names for GitHub messages | |
| */ | |
| const githubLabelName = 'GitHub' | |
| const githubPullRequestLabelName = 'GitHub/Pull Request' | |
| const githubIssueLabelName = 'GitHub/Issue' |
| #!/bin/bash | |
| cat << EOF | |
| ########################################################### | |
| # Workaround adb disconnecting issue on macOS Sierra | |
| # | |
| # More info: | |
| # https://code.google.com/p/android/issues/detail?id=219085 | |
| # credits to: hans...@meetme.com, vs...@google.com | |
| ########################################################### |
| RN < 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache | |
| RN >= 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-native-packager-cache-* && rm -rf $TMPDIR/metro-bundler-cache-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache | |
| RN >= 0.63 - watchman watch-del-all && rm -rf node_modules && npm install && rm -rf /tmp/metro-* && npm run start --reset-cache | |
| npm >= 5 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache verify && npm install && npm start -- --reset-cache | |
| Windows - del %appdata%\Temp\react-native-* & cd android & gradlew clean & cd .. & del node_modules/ & npm cache clean --force & npm install & npm start -- --reset-cache |
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
- Open
C:\Program Files\Logitech\SetPointP\players.ini - Add these lines to their respective sections
[Players]
GooglePlayMusic=key,chrome.exe,Chrome_WidgetWin_1,xxx,xxx,&0xB3,&0xB3,&0xB2,&0xB1,&0xB0,0,1,Google Play Music
# If you need support for a third party Chromium browser, for eg. Vivaldi, add this line
Vivaldi=key,vivaldi.exe,Chrome_WidgetWin_1,xxx,xxx,&0xB3,&0xB3,&0xB2,&0xB1,&0xB0,0,1,Vivaldi
# Basically you need to copy paste the line, change the "exe file name", the entry name ( before = ) and the last part after the ,
[Players.Run]