- Healthy culture. A software project is its invested maintainers, and they’re also responsible for maintaining the culture.
- Virtue abounds. Everyone on the team really really cares about doing a great job.
- Awesome documentation, and clear/sensible standards around same.
- Easy to test. Easier to test than not test.
- Easy to code. New developers can get code, run apps/services, change/commit code their first day on the job.
- Extant coding standards.
- Extant tool to lint code (ensure conformance to coding standards). Integrated with source control so you can spot lint errors before you commit.
- All tools work with any dev setup–they are not tied to any operating system nor IDE.
- Distributed, modern source control.
- Continuous integration. Every commit on every branch is automatically tested.
- Issue tracking.
- Integrated source control, continuous integration, and issue tracking.
- Well-crafted, useful automated tests.
These are my email etiquette rules. I’d love to hear your own email etiquette rules, too.
Please call me if I fail to follow any of these simple rules. Literally. Like, pick up the phone and call me. Or tell me in person.
- Always reply to a personal email written to you.
- If several questions are asked in an email, address them all.
- Do not allow the body of your email to be smaller than your signature.
- Care. For instance, use proper grammar, spelling, sentence structure and capitalization.
There are of course exceptions to the first rule, such as when the email is ending a conversation. It may help to consider not replying akin to ignoring someone trying to talk with you.
Disclaimer: I know approximately jack squat about speculative investing, and only slightly more about how Bitcoin works. Be prepared to lose.
If you decide to buy one (or some) Bitcoin as an investment, here’s my (USA-specific) advice:
- Buy Bitcoin via Coinbase. It’s easy and works with a standard USA checking account. Write down your purchase details for tax purposes.
- Don’t leave your Bitcoin at Coinbase. Create a paper wallet and send your Bitcoin to that.
- Lock the paper wallet away in a safety deposit box and forget about it.
I’m not sure how to properly pluralize “Bitcoin” so I didn’t bother ever adding an “s” in this post.
Last of all, consider actually using Bitcoin, instead of just investing! It’s complicated. It’s scary. You will be challenged. You’ll learn about some interesting subjects, and you’ll be on the forefront of what is surely a revolution in currencies.
It appears Coinbase paper wallet private keys are in a proprietary format, so my “easy” method won’t work. Here are instructions to really trade your Casascius physical Bitcoin for U.S. dollars.
- Obtain the private key. Carefully remove the hologram sticker from the back of the physical coin. A bunch of letters and numbers are printed on the back (example). Those letters and numbers comprise the “private key” for a Bitcoin wallet containing some amount of Bitcoin(s). Whomever possesses this private key may send any fraction (as little as 0.00000001) of the wallet value to another wallet.
- Create a wallet on Blockchain. https://blockchain.info/wallet/new
- Import the Bitcoin to Blockchain. In your Blockchain wallet, click “Import / Export”, then paste the mini private key from your Casascius physical Bitcoin under “Import Private Key” and click “Add Private Key”.
- Sign up on Coinbase. Use this referral link and I’ll get $5 after you exchange 1 Bitcoin.
- Send the Bitcoin to Coinbase. On Coinbase click “Send/Request”, then “Request Money”. Leave the form blank and just copy the address. In your Blockchain wallet click “Send Money” and use the address you just copied.
- Sell your Bitcoin for USD. This part is pretty straightforward. Click on Buy/Sell to sell your Bitcoin and transfer the USD to your bank account.
UPDATE: it appears Coinbase paper wallet private keys are in a proprietary format, so the procedure in this blog post doesn’t work. Try this instead–I just tested it, so I know it works!
The Seattle Police Department has a great service called Tweets by Beat where one can freak oneself out at how much crime is occurring everywhere.
Beat:N2, NOISE DISTURBANCE at 9XX BLOCK OF N 91 ST reported on 8/30/2013 5:53 AM, Call# 13000314109
— SeattlePD Nora2 (@SeattlePDN2) August 30, 2013
Notice no links are included. To get the details, visit police headquarters and ask for help. Have the information in the tweet handy–you’ll need it for the paperwork. Don’t mention “tweets” or Twitter or Tweets by Beat because you might as well be speaking Klingon. Just say you saw/heard something happen and want the 911 call and incident report. They’ll help you fill out the paperwork, and they’ll provide the relevant public records within 5 business days.
Here’s my wishlist for you.
- connect/partner with more banks for tighter integration than ACH
- get accepted at some big-name merchants
- The Internal Revenue Service
- support two-factor authentication
The Seattle Disaster Relief Trials was a blast! Great idea, Jesse.
The balloon got wedged into my helmet at the 1st checkpoint and just stayed there the whole ride.
There’s also a *very* brief cameo of me buckling in a bucket of water at the 2nd checkpoint (1min 52sec in) in http://q13fox.com/2013/06/21/bike-heroes-prepare-for-disaster/
If a friend’s email account is compromised and used to send spam or phishing emails to my gmail address, should I click “Report spam” or “Report phishing” for those emails in the gmail web interface?
I’m thinking I should, but I’m worried it will mess up my friend’s email score/reputation/whatever and make it painful for them later if they recover their compromised account.
Then again, maybe that’s a fair consequence for letting their account get compromised. Unless of course their email provider was compromised, which would mean it wasn’t their fault (unless they chose a notoriously bad email provider).
(side note: when I notice a friend’s email account is compromised, I immediately contact them via some other means–for example: call them–and let them know)
The Bluehost hosting account must be configured to use a recent version of PHP. After creating a subdomain, I had to delete the .htaccess file to make sure the latest version of PHP was used.
I used the periodic cron method to update my feeds. I used the “twice daily” common schedule. Here’s my command:
/usr/php/54/usr/bin/php-cli $HOME/public_html/www.example.com/tt-rss/update.php --feeds --quiet
The explicit path is required because tt-rss needs a recent version of php meant for the cli (for example, with