Check out the Unfolding of Language if you're interest in the Language Instinct. Also Elephant in the Room made me think of the Master and his Emissary, very interesting book, check that one out too.
Yep great example, didn't remember to mention that too.
To expand on your point for others about mental exercises: if you experience pain, say, in your leg during a squat, if you mentally visualize doing a squat, and imagine doing it while not feeling pain, and practice doing that visualization, that will help you feel less pain when you actually get around to doing a squat.
Another way I've heard people treat phantom limb is by getting a tall standing mirror, so that their other limb in the mirror looks like their missing limb. And then they will move their limb and that will help treat the pain they feel in their phantom limb.
I haven't checked out Healing Back Pain: The Mind-Body Connection but if you want another book that I think speaks from a similar angle, and that I know has a scientific grounding, check out A Guide to Better Movement by Todd Hargrove[1].
The crux of some recent research into pain can be summarized in a few points:
* Sometimes you'll hear patients talk about pain and look at their area of pain and find nothing in their bones/muscles/etc that would indicate they should experience pain, and sometimes you'll look at other patients and their bones/muscles/etc and find they should experience pain but they don't.
* If you have three cups of water–two of them warm, the middle one cold–and stick a finger in each cup, your finger that is in the middle, cold cup will actually feel a hot, burning sensation. Try it yourself. Pain can be misleading and not indicative of actual danger.
* Similarly, ever play a sport and not feel an injury until the next day? (I'm not talking about soreness.) This indicates that pain can be silenced, and that underlying physical damage doesn't immediately and directly cause a sensation of pain.
The mind-body connection in essence is this: your body is the territory, and your mind is the map. Your map of the territory can become out of sync with the way the territory actually is. The body is incredibly adaptable, if you teach your body to feel pain, it will, if you teach your body to move freely, it will. This doesn't mean, if you're feeling pain, go and do crazy things and hump the dragon so to speak. It does mean: approach the dragon. Lean into the pain. Allow yourself to feel pain. Recognize the pain and listen to it and learn more about where the flare-up line exists in your body. Constantly strive to elevate where the flare-up line is, mindfully and with good vibes. :)
Increasingly we're moving away from a past where physical pain is stigmatized.
That was it! Thank you so much, I kept googling skill share which would give me results for skillshare.com. So glad the first comment helped me find it, thanks again.
From my point of view, this is not too unlike what we have without Bitcoin. With USD or CAD, consumers still have to make a decision whether it is worth exchanging a number of dollars a point in time for something else when instead they can use that money to make more money and eventually have "30 bucks next year".
I can see how making more money with Bitcoin is different than with USD or CAD though, if I were to consider only what you've laid out. With the latter two currencies, I would have to learn about different investment strategies and figure out what would actually make me more money, things as a consumer I don't even know about. But with Bitcoin, I could just hold onto them and except to have more money in the future.
What I am trying to say is I don't think what you've laid out is something new, this incentive–to hold onto money so I can more the future–already exists with our currencies today, but Bitcoin happens to give a little spin to that incentivize–which is it'll easier to have more money in the future.
I would love to hear from a real economist too but I don't think it hurts to take our brains out on a little walk.
Hey, I've started to learn about devops and systems administration recently and I've learned a ton in this thread and this article, so thanks for that and thanks to everyone else.
But do you know of any good resources to learn about those two things? And I'm taking about basic devops, before you even start worrying about automating, and the things you would actually automate–because I don't know what it is I should be doing in the first place.
Things like what you should be doing right after you SSH into your server, how to make your server secure, how to use nginx, chmod'ing permissions of files correctly, and things I don't even know about.
Is there a One Month Rails or Michael Hartl's RoR Tutorial for devops/sys admin?
Regardless, thanks for taking the time to read this :)
This is off-topic, but because I've just recently started my foray into devops/systems administration do you know any lists of good resources to learn about those two things? I'd love to see a guide like this [1] except that's for analytics.
Things like what you should do right after you SSH into a server, how to make your server secure, setting up nginx, chmod'ing permissions of files correctly, and things I don't even know.
Regardless if you get back to me, I appreciate you taking the time to read this :)
I disagree. I'd say the free month is not for a tweet, but for the number of users who sign up because of your tweet and then how much those users end up paying to use the product. If just one user signs up because of your tweet and pays to use the product for a month, then what's been given away has been earned back. And none of this says how much the product should be valued quantitatively, i.e. how much one month is worth.
On the other hand, you do comment about perception–if the users perceive the product to worth less because of this deal, "a tweet for a free month", the rationale behind why the deal is good for the product might not do anything to offset that loss in perceived value.
Huh, I thought you could use a beta phase to promote the app for the opposite reason—by having a beta phase you can have a huge release to the public, as opposed to marketing the app must be a revolutionary idea because it's in its beta phase.
Which makes me want to ask: does a beta phase mean it's only open for use to those who've requested and have been given access? Or can you have an app in the beta phase and also have it open for everyone to use?
Your comment reminds me of this discussion I had before here on HN and someone made a reply that has stuck with me to this day in its eloquence. I'll quote it here because I want to share what comment I'm talking about but out of context I think it makes little sense and I think you should read the thread [1]–it's very relevant to what we're talking about here.
> Essentially it is trying to say that we are at a global maximum in a space that is probably more nonlinear. In fact our genes may well be suboptimal in some respects even if you think they have "control".
The Machinery of Life [1] is a fantastic book, I was one of those curious laymen and boy did it saturate my thirst for learning about microbiology. I think it's close to the time I read it again.
