That's "mediocre" at best. This should be The One Password To Rule Them All, the only one you'd actually need to remember (or be completely locked out of the password archive if you forget!). So: using a pass_phrase_ would definitely be good, but it would need to be a good deal longer. I'd suggest at least eight to ten words. (Note that this is The Key to all your other passwords - it needs to be both strong AND memorable; no point in compromising one for the other.)
Today I decided to learn about Go. I knew nothing prior. I read a few chapters of Chikun's "Go: A Complete Guide to the Game." I really like how he goes back and forth between introducing a game mechanic, and then some historical element.
You cannot make bitcoins with a shitty CPU, or a shitty GPU. You can try, but the difficulty is too high, and is always increasing.
If this is a new concept to you, imagine:
When I first received my BFL Jalapeno (ASIC 5G mining rig) and started mining, to the time I sold it, the difficulty had increased enough that I was seeing a .05 BTC gain in twice the time. So now you can imagine how eventually only people above a certain mining speed will be profitable.
At the next difficulty estimate, an i7 with free electricity mining all the time at 8 MH/s would make about 9 US cents in a month. Since the difficulty will probably go up again in less than two weeks, make that less than 2 US cents per week. Since very few people actually have free electricity it's not worth it.
Okay, in the hypothetical world where 1 satoshi is worth some huge amount of USD more than it presently is, if you suck up the electricity cost now (which I believe would be less than $1 USD per day for an i7) you can get a few satoshi that may one day make that up-front cost worth it...
Whether you can actually get a single satoshi from a pool is another story. If the pool uses PPLNS, you might not ever. I think most would object to you for being misleading. If you want bitcoins, buy them, or get an ASIC miner and don't use a sucky-ass CPU or GPU.