Something similar happens when riding motorcycles. At first you're cautious because you don't know how to evaluate the risks. Then you move into a peak of overconfidence where the usual risks are known; but this is the most dangerous period. It's only after a while at this level, perhaps after a few scares or accidents, that a new appreciation for unusual risks starts to come in. You start to become less optimistic, and consider what could go wrong, not just what's likely to go wrong. You start actively seeking reasons for the traffic around you to do the unexpected.
Mature evaluation of risks increases the weighting given to tail events, black swans etc., particularly if the outcome is severe. Teaching this perspective ought to be effective in keeping it in mind for the teacher too.
My Dad - who used to drive an Ambulance then Fire Engines (for about 20 years) - taught me to drive and use something called "Defensive Driving Techniques". Where most people look at one or two cars ahead and hopefully the one behind, my Dad taught me to look at every car that I can see, using every gap, window, mirror etc to be aware of my surroundings. Look at people, bus stops, crossings, shops in towns etc.
He also suggested that rather than just looking at a car, you look at the position of the car, who's driving, the age, have I seen them drive weirdly yet? This way you can build up a much better mental model of how they're going to react to something. This has saved me numerous times where I've judged what a car will do just by how they're placed in the road, even if they look like they may do something else to a normal driver.
It's a technique that I've shown to my girlfriend and it's changed her driving (for the better) and what I'll be teaching my kids when the time comes.
I've heard Defensive Driving described as driving with the assumption that someone else is going to do something wrong, and to be in a position to defend yourself from that eventuality.
The opposite is to drive Offensively (ha ha) which I guess is to assume that every other car will do the right thing and it's okay if I take a few risks.
I wouldn't say that at all since you're not assuming people are going to do something wrong per-se, you're more willing to accept that a situation that looks normal is going to turn out differently and be aware of how you can avoid any driver who's going to do that stupid thing.
...look at every car that I can see, using every gap, window, mirror etc to be aware of my surroundings. Look at people, bus stops, crossings, shops in towns etc.
In my experience a shortcut to this level of awareness is to regularly cycle in commuting traffic. Not only does one notice much more, but one also notices the classes of things that it's actually impossible to notice from an autocage. (Examples: what most drivers are doing in addition to driving, where pedestrians are hiding, how a line of traffic moves through signals in fits and starts, etc.)
That's a kind of brute force approach. It seems sub optimal but I don't know how to reason about it.
Should I say that observing every vehicle across the median on the oncoming carriageway is inefficient? Well I can't say that because occasionally some small cargo or even a wheel falls off and bounds across to the oncoming lane - something you definitely want to see coming.
Perhaps taking a zonal approach is as effective and certainly less taxing on the driver.
Scan each zone, some zones get scanned more frequently, and look for anything unusual.
Defensive driving is really just a specific application of situational awareness [0]. With practice and experience you'll go from just maintaining visibility and space for reaction time to actually remembering where drivers are that have been blocked from your view by other vehicles. You never really track every vehicle and pedestrian, but you do make note of particular ones and the rest get lumped into groups based on their behavior. You'll learn to anticipate the car that's going to make a left turn in front of you by taking your foot off the throttle earlier instead of braking at the last second.
you're talking about chunking: at first you try to remember everything, then as you gain experience you learn you can abstract certain items away to a general model of them (chunk) without having to remember the specifics of each individual item.
Like everything related to driving, it eventually becomes automatic.
It's not that you're consciously looking at each car and saying "Is this car going to be a problem? Is this one a problem?" Instead, you recognize patterns. If a car suddenly weaves out of its lane, it triggers a tinge of fear and you give that car a wide berth until you can pass him and leave him behind. If you see brake lights go on 10 cars ahead of you, you know that you're going to have to slow down, so get ready for it (oftentimes, I'll let up on the gas as soon as I see brake lights go on a quarter mile down the road, and by the time I get to the traffic, I'll be going their speed anyway). If you're in a car's blind spot, pay extra careful attention to turn signals or any deviation from his lane, and try to pull forward or behind so he can see you. If a car is clearly in a rush, it's a good bet he's going to weave in front of you, so hang back and make sure you have room to adjust if he does. If two cars try to enter the same spot in the same line (this is my personal biggest fear, they're both in each other's blind spot and each has reason to believe the lane they're switching into is clear), hang back, and honk if it's clear that they don't see each other.
It's about pattern recognition, knowing which situations are dangerous so you can be extra careful whenever it looks like one of those situations is happening.
"That's a kind of brute force approach. It seems sub optimal but I don't know how to reason about it."
Well, what else are you doing while driving?
For the most part, whatever your answer is to that question, stop it. (Reasonable exceptions apply; conversation with another in the car isn't too big a deal, of course.)
Now that you're just driving and not doing anything else, you might as well be active about it and be on the lookout for long-tail risks, since really long-tail risks are all you ever have to worry about. Driving is fairly safe and almost everything that ever happens bad is long-tail in the first place or we wouldn't drive.
Agree 100% with "if you are doing something else while driving, stop it". I have always thought the conversation is the distracting part, not the act of holding a phone to your head. Research shows that it's less distracting to talk to a passenger than a phone conversation: http://scienceblogs.com/cognitivedaily/2007/01/24/want-to-dr... (link in article). Still, I prefer to remain focused on the driving conditions.
I'm not sure I agree that "driving is fairly safe" though. We have mitigated much of the risk associated with driving with vehicle impact standards and road design. I still really feel that most drivers don't understand the magnitude of what they are doing - they become accustomed to the relative safety and start doing other things. It seems the more safety we "build into the system" the more risks people are willing to take. I'm not suggesting we take safety out of the system though!
I learnt these techniques from the IAM [0] in the UK. Their manual is Roadcraft - the Police Driver's Handbook [1] which introduces techniques which I've found incredibly valuable.
I use that technique, and during a period in which I commuted, my meditations on cars taught me to use the same principles of thorough research and prediction to analyze stocks, which worked out well. It can also apply to understanding a room of people or a crowd. Those are all situations where overconfidence can be worse than overcaution.
I think defensive driving is a good way to introduce that kind of prudence to people who would otherwise not pay close attention to things because piloting an auto is frightening at first so makes a person receptive to whatever makes them safer and gives them confidence.
Even beyond that, there's an overall 'field' of cars for me. Peripheral vision gets an overall sense of all cars in the proverbial neighborhood, and looks for scary patterns. Little things that seem harmless (and maybe are) put me on edge and make me guard my brake.
My wife didn't understand at first, but after 12 years of driving with zero accidents, it becomes apparent that it works.
I came to make a similar comment regarding my hobby; skydiving.
I've been falling out of planes for over 20 years, and have seen the equipment progress in design and function such that people don't die due to the same things which used to claim skydivers. However the yearly rate of death remains about the same. The dark joke is that as the sport has gotten safer people have had to come up with new, more stupid ways to die.
Smarter people than me point to the theory of risk homeostasis. Basically, you accept a level of risk of an activity, if the safety of this act increases you'll find new ways to make it as risky as it was previously.
What about the overall risk on a motorcycle? I have two friends who were killed on motorcycles. Both were experienced, in neither case was it their fault, and I'm not sure if they could have avoided it. Seems unlikely. But what I do know is that if they were driving their cars, they would be alive today. I find people often correctly evaluate the risk of failure (low), but completely ignore the potential cost (your life) . I'm guessing they also have a different model for calculating reward, but it seems mostly an error in calculating risk and cost. BTW, these were IT guys in their 30s, not teenagers.
I've had an accident on a motorbike which ended up thankfully only with a broken leg and two months of immobility (the fracture was a bit complicated). It was not my fault and if I was in a car, I probably wouldn't have been hurt at all. Roughly a year after the accident, I started to ride the motorbike again, albeit not that often. I don't see anything I could easily improve with the driving style to reduce the risk. I think I'm already quite defensive both on the motorcycle and in the car and I try to always remind myself that I'm no expert.
Maybe I don't correctly evaluate the risk or I just assign too much value to the benefits I get. It's very hard to calculate with a cost of own life. Moreover this cost is changing. It can temporarily increase for example when you support a family. But how do you account for the fact that you have a finite amount of time here no matter what you do? There are much less risky things to do and also much riskier ones than riding a motorbike. Are all the people who take more than the smallest possible amount of risk crazy or unable to assess the values? Honestly, I still don't know.
Motorcycles aren't called "donorcycles" for nothing. The risk level seems to be intrinsically high, though it seems to be held up by bikers not wearing helmets:
The documented risk of dying from a serious head wound while riding without a helmet is so high, bare-headed motorcyclists are considered ideal organ donors: They're typically young, otherwise healthy and at high risk of brain death from sudden trauma.
Certainly riding a motorcycle is risky. Lots of things people do for fun have very large downsides (death or otherwise). Some of us feel the risk is worth the reward. I totally understand if you don't agree.
In terms of experience - I see a LOT of experienced motorcycle riders that have "1 year of experience 10 times". I'm not saying that I'm a better rider than other experienced riders, however motorcycle riding is something that requires constant discipline (moreso than other forms of transportation that people generally do).
edit: Please don't take this comment as any indication of your friends experience. I'm speaking in generalities.
Just how dangerous do motorcycles have to be before the fun isn't worth the risk? Twice as dangerous as cars? 5 times? Maybe 10x? Surely not 20 times more dangerous?
From Wikipedia's article on Motorcycle Safety: Per vehicle mile traveled, motorcyclists' risk of a fatal crash is 35 times greater than a passenger car.
Motorcycles are insanely dangerous. There are 23 fatalities per 100 million miles ridden in the US. If you ride 4,000 miles a year for 40 years, that gives you just over a 4% chance of dying. Compare to a 0.1% chance for doing the same in a car. And that's just the risk of death. It doesn't include risk of paralysis, brain damage, or losing a limb. Even if you are a perfect rider, half of all fatal motorcycle accidents are collisions with cars. Many of those simply cannot be avoided.
People would rightly call you insane for driving a car that had 35x more fatalities than average. I fail to see how removing two wheels makes it OK.
(Note: I've been riding for seven years and had no accidents. There are some good reasons for riding a motorcycle, but they don't involve recreation.)
Horse riding is about 10x more dangerous than motorcycles, according to stats I've seen.
Motorcycle touring is my primary leisure activity. It's what I do during summer holidays. A 300cc scooter is my primary means of travel in London. Riding on motorized two wheels is so integrated into my life that it would be hard for me to imagine a life without it.
It's almost a physical need. After a few days of snow, or a spending some time somewhere without a motorcycle, I start getting cravings. I'll frequently go out for a wander on weekends for no other reason than to ride.
Riding has a meditative quality. You can't think about anything else; you're forced to be in the moment, in flow, in a constant planning and reactive mode. Worries and concerns and any other busy thoughts disappear.
You are correct of course. I've ridden for 20+ years with only one fall in an empty intersection (gravel) and rode away with literally only a scratch. I'm pretty sure those days are over though as my wife is not a fan, and I recently sold my motorcycle.
I've noticed that some curve in software engineering and systems administration, at least from people who are trying to be serious.
At first, everything is new and scary, so they'll ask for help with even basic things, and maybe keep meticulous notes or comments about what they're doing.
Later, after they've gotten more and more comfortable, they'll stop keeping good notes and asking for help.
Finally, after being bitten in the ass a few times, they'll start to regard all computer systems as being in active conspiracy to make their life and their code miserable, and at last they'll finally have the correct mindset to get quality work done.
When I got my motorcycle license I was told that the probability of an accident happening increases a lot after 6 months / 3000 km (~2000 miles) due to the recently gained confidence. I have no idea if those stats are even remotely correct but it made sense at the time.
I think the idea applies to cars as well, fwii the worst year for car accidents is the 2nd year after getting a licence (1st year being the worst), at least in some countries (can't remember where this is from)
Richard Feynman attributed to this phenomena, although he did not name it as such. Paraphrasing here, but he did not accept a position at the Institute for Advanced Study precisely because it would no longer allow him to teach. Or to be more precise, he wanted to always be in a position that would make him teach, forcing him to rethink the basic ideas.
Its interesting that I was just having a conversation about this yesterday. In today's world, you simply can't stop learning after you've got a job. You have to keep learning, not only new technologies, but also revisit the fundamentals every now and then. To be sure, if you work in a field that you like (as I do) it is much easier to do this. If not, you can rationalize the time investment as going towards making you better at your job.
This is so true, and goes the same for every job. I saw expert developers push stuff right into master and deploy it without testing because "they know what they do and you have to be productive".
I get nods when I demand some form of automated testing because "everyone's IQ and experience tends to become irrelevant at 3 am when you're tired and hungry working on a critical bug before the release ships." I ask people if they trust that developer, not the usual person you know. Beyond that, there's few better ways to show how to use a piece of code than by writing a test that actually does use it as you would, so it cuts down on some documentation if people can trust that it'll be there.
That must depend on your work environment. I do his a lot, but I work on an in house app, with around 40 users. I have user acceptance testing rather than unit testing, and it catches far more bugs. If I do mess up, it is easy enough to roll back.
We are short of IT staff and the lab staff seem to have more free time. Why not involve them in the process? I communicate with them, get to understand what they need better, and save time on writing tests that would probably be obsolete a few months down the line, due to the rapidly changing nature of our business. "Individuals and interactions over processes and tools".
Coding to best standards is a nice ideal to have, but in almost every place I have worked getting something working quickly has been a far higher priority.
One practical definition of an expert is someone who can achieve good outcomes even while, or because of, breaking the rules. Great writers break "rules" of grammer all the time, sometimes even basic ones in the case of folks like e.e. cummings or Cormac McCarthy.
Why do we have rules at all? If we all knew everything about everything, then we wouldn't need rules; we'd just make every decision correctly on our own. But we don't know everything about everything, so rules provide simple heuristics to guide our behavior.
But sometimes a person knows everything about 1 or 2 things. And in those things, if they really know what we're doing, they don't need rules, because their understanding exceeds simple heuristics.
So, I think the word "expert" is misplaced here, which is IMO part of the problem. Just because you've done something for a long time, that doesn't make you an expert. And expertise is a narrow lane--an expert in bricklaying might not be an expert in construction safety.
All that said, I have found that teaching is a great way to develop personal competence. But it's not because I'm lazy, it's because teaching forces me to examine the rules, and the basis for their creation, which builds real competence and ultimately expertise.
Looking at WP, I think they overstate the importance: https://en.wikipedia.org/wiki/Al_Capone#Trials It sounds like various local governments just began throwing the book at him on any charges they could trump up, until negotiations with the IRS went terribly wrong and they had an admission of his income levels which they could use against him and make real charges stick. (And then syphilis meant he was no longer a threat.)
Yeah that story conveniently left out the part where he had neuro-syphilis and was slowly becoming more and more retarded. At the end he had the intelligence of like a 4 year old.
I doubt he was all there when this was going down.
Early on at Thinkful we were concerned about being able to consistently find skilled mentors to work with students learning front end web development. We hoped expert developers would find our model of mentorship personally and professionally rewarding but we were far from certain. We've built an outstandingly talented team and I attribute much of our success to filtering specifically for those developers and designers who've already come to this realization and decided to act on it.
A student always fails exam. And takes extra classes - the professors explains and explains. But the student - "I don't get it, I don't get it". Finally the professor loses his mind "Oh, come on - I already got it from that much explaining"
1) constantly compliment, in extremely general terms, their employees : "The world is better off without Capone’s expertise, but it’s not better off without yours", "how even the smartest people in the world can destroy their lives and careers with a tiny mistake". But only in general terms.
2) their only purpose is to increase their own money : "We were obsessed with safety. Insurance for construction companies is extremely expensive; one way to stay competitive was to make sure no employees got hurt". The article itself is just attention-grabbing, and it's obviously succeeded with very little actual content.
3) Between the lines it is clear what they really think about their employees : "You see, you’ve been blessed with the ability to think, reason, and do math". In other words, he thinks his (ex-)employees are morons. "That’s how the brain works—it fears what it doesn’t understand.". He proceeds to "explain how your mind words", again patronizing, childish and confirming his own superiority.
4) They suggest having the solution. Just read the titles "How To Stay On Top Of Your Game And Never Make Rookie Mistakes", "Why You Suffer From Lazy Expert Syndrome"
5) Of course, they don't have the solution. The problem is that the solution is the point where the good balances out the bad. Where your way of working prevents you getting fired, or even gets you good review, but otherwise is as little work and as little risk as possible. But of course, there is zero guidance in the article about where to find this point.
Probably there's 2 reasons for this. Firstly, they don't want you to think in your own interest. The interest of the manager comes first (I'd say the company's interest, but let's be honest here), and that means maximizing output (as alluded to in the skills of an expert cook. Inaccurate, of course. My dad's a cook and I've asked this many times. The thing that distinguishes an expert cook is consistently good food. NOT more of it, even though a significant part of training for cooks is how to increase food output to a point without degrading quality too much. But consistently good food, that's bloody hard)
6) Due to lack of a solution, an extremely general advice is given. "Become a mentor". Right. Supremely unhelpful of course. Like all of management. You could make a list of 10 inspirational lines and you'd have a good summary of hundreds of terabytes of these pieces.
Also, I've studied AI and the idea that the brain "fears what it doesn't understand". That is just so wrong it's ridiculous. When you train a person for something new, what happens is that the higher (and MUCH slower) brain processes train the lower ones to perform a task. There is no fear involved (in non-extreme situations, not talking about learning to skydive here), there is simply switching from working from an abstract model (e.g. from a book, from a trainer) to working in an extremely non-abstract situation (the real world). For abstract models, the brain is very, very slow, inaccurate and also very, very much non-parallel. Non-abstract reflexive models - very, very fast, extremely accurate and massively parallel (10-15 neurons involved at most in decision making, you can combine it with dozens of other tasks without effort, very fast and appears even faster because the brain responds to it's prediction of a future situation, not to the impulses it's actually receiving, creating the -usually good enough- illusion of infinitely fast reactions as long as the prediction is accurate (e.g. nobody has a brain fast enough to make a tennis racket track a tennis ball. That is impossible with a feedback loop that takes 0.10-0.15s to react, it needs thousands of hertz. Yet lots of humans do so). And of course, hilarity ensues, often painfully, if the prediction is wrong).
Mature evaluation of risks increases the weighting given to tail events, black swans etc., particularly if the outcome is severe. Teaching this perspective ought to be effective in keeping it in mind for the teacher too.