Another week has passed:
- Unlike in Windows; in Chrome you cannot easily focus on your bookmarks bar with a keyboard short key on Mac OS X.
- If you want to run rake tasks in your specs in a before block, be sure to set a line
Rake::Task[name].reenable
so you can re-execute them every time. Rake seems to remember which task has been executed, so you cannot execute it twice.
- If you want to stub out STDOUT messages (like with ‘puts’) in your spec, use:
STDOUT.stubs(:puts)
- When in doubt, speak up. Always.
- With Scrum, big stories are big risks. Split them up.
- Don’t use PID files to remember which proces has been started and when it should be stopped. Especially if you want to reboot a deamon process automatically once it has died. Instead wait for it when the deamon has quit and act upon a not-normal exit code.
- Sometimes using ‘git fetch -p’ is not enough to prune all your local branches (which do not exist anymore on remote). You can use a rather long command (see below, from stackoverflow question)
git branch -r | awk '{print $1}' | egrep -v -f /dev/fd/0 <(git branch -vv | grep origin) | awk '{print $1}' | xargs git branch -d - With editorconfig (*) you can create code formatting rules, nothing new here, but editorconfig has plugins for a lot of known editors, (I tested it in Vim & Sublime), meaning you can now share these rules cross-editor. Now that is cool!
- With C++, when your function argument is using const, and you’re calling a non-const function on that argument you will end up with a message like:
“error: passing ‘const xxx’ as ‘xxx’ argument of ‘function you where trying to call on xxx’ discards qualifiers”.
You can fix this by telling the function body is const:
bool myFunction() const { /* code here */ }
* Thx to Arjen about editorconfig.