All of boggler's Comments + Replies

Yes! This is what I was gesturing towards. I agree with this.

This is really cool! Thank you for sharing. I think micromorts will significantly help my intuition.

At least with regards to my own notions of "badass," I think this is only sometimes true. I do not think it is considered badass to watch a horror film, yet there is substantial S1 perceived risk.

7gjm
X's perception of Y's badassity is about X's S1 perception of Y's risk. If I watch a horror movie, it may feel risky to me but it won't to you, so you won't see me as a badass. More precisely, X's perception of Y's badassity is about X's S1 perception of the risk Y is knowingly accepting. So, if I watch a horror movie, the only person who feels any sort of risk or danger is me, and only while I'm watching it. (Maybe for a little while afterwards.) Will this make me feel like a badass? Probably not, because what generates the sense of risk is (so to speak) entering into the movie's world, and while I'm doing that I'm not attending to my own actions at all. (I suppose I might seem very very slightly badass for watching something that is predictably going to scare me. Or, if not, I might seem like a wuss if I conspicuously avoid watching the movie.)

I love the Chinese saying!

And your point is interesting. I believe my desire to ride a motorcycle stems from the motorcycle being seen as a cultural symbol of badassity as opposed from the inherent danger of riding a motorcycle. And, while badassity may coincide with danger, the two need not be correlated.

For example, I view skydiving as a symbol of badassity, but skydiving in relation to driving an automobile (generally not very badass) is quite safe.

I wonder if I am unusual in this respect, and perhaps it is more common to be attracted to motorcycling precisely because of the danger.

6Qiaochu_Yuan
Badassity is about S1 perceived risk, not actual risk.

Although, I haven't explicitly done test-first programming, it appears as though it could be a great way to remove the trepidation. I do, however, often work on problem sets for school which come with pre-written tests, and I find myself mildly anxious before I run those tests on my code. Perhaps, the problem here is that I have internalized that code is "done" when the last line is written, as opposed to the test-first paradigm where "done" necessitates passing all the tests.

How do you feel in that space between completing your last line of code and running your first test?

1PeterBorah
This reply is extremely late, but I'm annoyed at myself for not having responded at the time, so I'll do it now in case anyone runs across this at some point in the future: I guess I feel a little trepidation or edge-of-my-seat feeling when I first run a test (I have surprisingly often ended up crossing my fingers), but I try to write tests in a nice modular way, so that I'm never writing more than ~5-10 lines of code before I can test again. I feel a lot more trepidation when I break this pattern, and have a big chunk of new code that hasn't been tested at all yet.

Noting: I feel trepidation towards testing my code. I believe this is because I suspect that my code has bugs and bugs are equated to debugging (i.e. work). Yet, once I get over my trepidation and test my code with all the supplied test cases, I become giddy and want to test everything. I believe this is because I feel that my code is free of bugs and every test is then a testament to what I've created. Has anyone else experienced something similar?

2PeterBorah
Hmm, maybe this is part of the motivation for test-first programming? Since I was originally trained to do test-first, I don't have this problem, because there are always already tests before I write any code. And I pretty much always know my code works, because it wouldn't be done if the tests weren't passing yet.
3habryka
Yep, I love testing when I've just done it a bunch, and hate testing when I haven't done it recently. I think a large part is just that testing actually requires a very different thinking style than coding, and I hate context-switches.
4Hazard
Though I don't often get super excited about testing, I have noticed that the number of false positives (I anticipate it being difficult, but it's not that hard) is higher than I want it to be.