- https://www.youtube.com/watch?v=i-oSr8ei4BU
- https://youtu.be/3SkCojauHto?t=1331 (Just watch the two piece anchor stuff)
{ | |
"65536": [ | |
"alphashift" | |
], | |
"131072": [ | |
"shift" | |
], | |
"196608": [ | |
"alphashift", | |
"shift" |
# frozen_string_literal: true | |
# Connection lifetime for ActiveRecord | |
# | |
# Make sure that connections to the database can only live for a certain number | |
# of seconds. Once lifetime is reached, the underlying connection will be | |
# reconnected. This is enforced when checking out a connection for use from the | |
# pool. Use in combination with idle_timeout to enforce connection lifetime on | |
# idle connections as well. | |
# |
In order of first appearance in The Morning Paper.
discussion https://www.reddit.com/r/thinkpad/comments/6var8o/blog_some_notes_on_x1c5_arch_linux/
dmi:bvnLENOVO:bvrN1MET33W(1.18):bd04/11/2017:svnLENOVO:pn20HQS0LV00:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HQS0LV00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.
# Set variables in .bashrc file | |
# don't forget to change your path correctly! | |
export GOPATH=$HOME/golang | |
export GOROOT=/usr/local/opt/go/libexec | |
export PATH=$PATH:$GOPATH/bin | |
export PATH=$PATH:$GOROOT/bin |
This is the latest version of an email which I send periodically, offering customers the opportunity to pre-pay for SaaS in return for a discount. The benefits to the SaaS company are better cash flow and reduced churn rate. The benefits to the customer are, well, in the email. This genre of email has produced hundreds of thousands of dollars in pre-pays for some companies I work with, and it rarely requires any more work than this example.
I've put $79 is as a placeholder for the cost of the user's plan. We calculate that for each account, naturally, along with the billing contact's name.
Subject: Save $79 on Appointment Reminder (and get a tax write-off) Formatting: 100% plain text. Gmail automatically links up the central link. From: Patrick McKenzie (Appointment Reminder) [email protected]