- Turn off notifications (ALT+click Notification Center)
- Turn off Bluetooth (in case someone sits on your Bluetooth keyboard/mouse, unless you're using Bluetooth of course)
- Turn off f.lux (can catch you out when using projectors)
- Prevent your computer from sleeping. Run Caffeine (or use settings to not let your computer sleep)
- Always run slides in presentation mode
/** | |
* 2019 @mvogelgesang | |
* This program is free software: you can redistribute it and/or modify | |
it under the terms of the GNU General Public License as published by | |
the Free Software Foundation, either version 3 of the License, or | |
(at your option) any later version. | |
This program is distributed in the hope that it will be useful, | |
but WITHOUT ANY WARRANTY; without even the implied warranty of | |
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
/************* | |
* colors.js * | |
************* | |
* | |
* You're almost at the exit. You just need to get past this | |
* color lock. | |
* | |
* Changing your environment is no longer enough. You must | |
* learn to change yourself. I've sent you a little something | |
* that should help with that. |
/**************** | |
* drones101.js * | |
**************** | |
* | |
* Do you remember, my dear Professor, a certain introductory | |
* computational rationality class you taught long ago? Assignment | |
* #2, behavior functions of autonomous agents? I remember that one | |
* fondly - but attack drones are so much easier to reason about | |
* when they're not staring you in the face, I would imagine! |
-
Respect Recipients' Time - This is the fundamental rule. As the message sender, the onus is on YOU to minimize the time your email will take to process. Even if it means taking more time at your end before sending.
-
Short or Slow is not Rude - Let's mutually agree to cut each other some slack. Given the email load we're all facing, it's OK if replies take a while coming and if they don't give detailed responses to all your questions. No one wants to come over as brusque, so please don't take it personally. We just want our lives back!
-
Celebrate Clarity - Start with a subject line that clearly labels the topic, and maybe includes a status category [Info], [Action], [Time Sens] [Low Priority]. Use crisp, muddle-free sentences. If the email has to be longer than five sentences, make sure the first provides the basic reason for writing. Avoid strange fonts and colors.
I hereby claim:
- I am matharden on github.
- I am matharden (https://keybase.io/matharden) on keybase.
- I have a public key whose fingerprint is E158 1408 E5A2 744C 8436 6B5D 39C6 3C94 4609 364E
To claim this, I am signing this object:
<ol class="progress"> | |
<li class="progress--completed"> | |
<div class="progress__step"> | |
<span class="progress__label">Prisoner details</span> | |
</div> | |
</li> | |
<li class="progress--completed"> | |
<div class="progress__step"> | |
<span class="progress__label">Visitor details</span> | |
</div> |
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE | |
Version 2, December 2004 | |
Copyright (C) 2011 YOUR_NAME_HERE <YOUR_URL_HERE> | |
Everyone is permitted to copy and distribute verbatim or modified | |
copies of this license document, and changing it is allowed as long | |
as the name is changed. | |
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE |
cd ~/Apps/app-name | |
heroku pgbackups:capture | |
curl -o $(date "+backup-%Y-%m-%d.dump") `heroku pgbackups:url` |