In today's episode, we talk about a phenomenon called the Einstellung Effect. Today's episode is brought to you by Linode. Linode Provides superfast SSD based Linux servers in the cloud starting at $10 a month. Linode is offering Developer Tea listeners $20 worth of credit if you use the code DEVELOPERTEA2017 at checkout. Head over to spec.fm/linode to learn more about what Linode has to offer to Developer Tea listeners .
In today's episode, we talk about a phenomenon called the Einstellung Effect.
Today's episode is brought to you by Linode. Linode Provides superfast SSD based Linux servers in the cloud starting at $10 a month. Linode is offering Developer Tea listeners $20 worth of credit if you use the code DEVELOPERTEA2017 at checkout. Head over to spec.fm/linode to learn more about what Linode has to offer to Developer Tea listeners .
Hey everyone and welcome to Developer Tea. My name is Jonathan Cottrell and in today's episode we're talking about the Einstellung effect. If you've never heard of the Einstellung effect, don't worry, you're probably in the majority. Most people are not sitting around reading Wikipedia articles about these cognitive studies that were done decades ago. But this particular study was done back in the 40s by a scientist named Abraham Luchen. And I hope I'm saying that correctly. It's either Luchen or Luchen. We're going to go with Luchen. But Abraham Luchen did this study to understand how people solve problems and not just how they solve one problem, but how they solve multiple problems and how the preceding problems affect the way that they solve the following problems. So the study was intended to understand the effects of solving one problem and then solving a next problem. How did that first problem's solution affect the way you solved the second problem? Now there were some very interesting findings. The way that the study was conducted was they gave the participants three jugs, three jugs of water or jugs that hold water. And each of those jugs hold a different amount of water. That amount was labeled on the jug and they would have to use those jugs in order to arrive at a particular amount in the largest jug. So let's say, for example, and these numbers are not correct, but let's say that they had one jug that had three ounces, one jug that had seven ounces, and one jug that had 12 ounces. And their job was to end up with 10 ounces in the 12 ounce jug. So the participants experienced a lot of difficulty in solving the problem. And they had to solve a series of these same, of these similar types of problems where you have to end up with a particular amount in the jug. Now the Einstellung effect is named after the German, the German word Einstellung, which means attitude or predisposition, right? So what Luchin found in his study was that the way that people solved the first problem, okay, the actual solution to the first problem was that the way that people solved the first problem was that the way that the way that people solved the first problem was that the way that people solved the first problem very often was used to solve the second problem. This is a very interesting finding. Basically, what he found was that participants, they had the ability with the jars that they had in hand to solve a second problem with much simpler procedure, right? In other words, much less work. But because they already had in their minds the solution to a previous problem, they had already found the same number that they're looking for in problem number two, they had run across that number in problem number one, their minds kind of short-circuited to that solution, even though it wasn't the most efficient solution. It wasn't the best solution to the problem, given the resources available. So the Einstellung effect is really a label for our mind's tendency to reuse the solution to solve the problem. And so the Einstellung effect is really a label for our mind's tendency to reuse the solution to solve the problem. And so the Einstellung effect is really a that we've used in the past on similar problems in the future without evaluating whether or not those solutions are the most efficient or the best solutions for that matter. Now, there's even more interesting findings that go along with Luchin's study. One of them, for example, is that this worsens with age. This is something we've talked about on the show before. It's just more evidence to show that our minds become kind of set in the right direction. And so the Einstellung effect is more evident in our ways as we get older, right? When we're very young, we are much more in learning mode and our minds haven't learned how to overly optimize what we're trying to solve, right? So we're evaluating all the time. We're re-evaluating, re-evaluating the problems that we're faced with. And we aren't reusing solutions as much because we're still in that evaluation mode. And what Luchin's study showed was that as people age, the older they became, the more likely they were to fall prey to the Einstellung effect. So in other words, younger children were much less likely to fall prey to the Einstellung effect. There's another very interesting finding from Luton's study. He found that people are able to rebound from the Einstellung effect, and perhaps most importantly, that the highest ability to rebound is found in people aged about 21 years old. In other words, once you recognize that you have reused a solution that wasn't optimum, then the next problem that you face, you are much more likely to actually rebound and create a novel solution for that problem rather than once again using a previously found solution. And this likelihood to rebound is greatest, around the age of 21. Now, you may be thinking, well, I'm too smart to fall prey to the Einstellung effect. Well, they did this study and eliminated differences between IQ as a statistical differentiator. In other words, your IQ level, your measured IQ doesn't change how susceptible you are to the Einstellung effect. One final interesting thing that I want to point out about Luton's study is that Luton's study is not necessarily a statistical differentiator. Luton's study, when people were constrained to a certain amount of time, in other words, when they weren't given an unlimited amount of time to solve the water jar problems, they were even more susceptible to the Einstellung effect. Now, all of us know that this has great implications for the type of work that we do because most of us, if not all of us, are probably under some kind of time constraint, right? We don't have an endless amount of time to solve the water jar problem, right? of time to deliver the code that we're working on. We don't have an endless amount of time to deliver features or to fix bugs. Usually, more often than not, we are time constrained in one way or another. So with the added dimension of stress, we are even more likely to fall susceptible to the Einstellung effect. And why is this such a problem? We're going to talk about that after a quick sponsor break. And we're also going to share the one thing that actually made a difference a positive difference in Luton studies. The one thing that actually kind of gave an uptick in people who were responding and rebounding from the Einstellung effect. We're going to talk about that right after our quick sponsor break. Today's sponsor is a very familiar sponsor to the show, Linode. Linode is such a great product because it's built on a very simple platform. And it's one that you've used whether or not you know it. Most of the web is, arguably, powered by Linux. And the simplicity of Linux is mirrored by the simplicity of Linode. You can get a Linux box up and running in the cloud in under a minute. This gives you the power of networked Linux. And it's only $10 a month for their introductory plan, which gets you, by the way, a very powerful box. It's not like you're buying a crippled box. It's a two gigabytes of RAM worth of a box. And it runs... on an Intel E5 processor stack. It also runs on an internal network that is 40 gigabits, which means it's super fast. If you ever networked two Linux boxes together, they're going to be talking to each other very quickly. So that latency is not going to be an issue if you end up running a networked system of servers, which, of course, you can do because Linux is incredibly flexible. You can do anything that you can do with Linux, you can do on Linode. Once again, their monthly plan starts at $10 a month. They do have caps on all of their plans. They have long view, tons of great features. You can go and check out more about what Linode has to offer to you at spec.fm slash Linode. Now here's another very important thing. One more thing I forgot to mention here is that all of these servers are running on SSDs, by the way. So you have solid state, very fast servers for just $10 a month. But if you use the special code developer T2017, you're going to get a lot of free stuff. So if you're going to at checkout, you're going to get $20 worth of credit. That's two months effectively for totally for free, just for using the code developer T2017. That's 2017. Go to spec.fm slash Linode to learn more about what Linode has to offer to you so you can start solving problems that really require your brainpower, like we're talking about in today's episode, the Einstellung effect. So we've already explained that. We've already explained that. We've already explained that. We've already explained kind of what it is. We have a tendency, a measurable tendency that gets worse as we get older. We have a measurable tendency to solve problems that look similar the same ways. Right? So as a developer, hopefully you've identified in your mind at least 20 different things that look very similar that you've used the same solutions for. Now, I want to make sure that you're hearing me correctly. There are many problems that can be solved by very similar solutions, right? What we're not saying in this episode is that you need to use a new tool every single time you solve a problem that is similar to one that you've solved in the past. There are different classes of solutions to problems, and you shouldn't view this episode as an excuse to go out and try a new tool every single time you encounter a new problem. That's not the point of today's episode. Instead, we're talking about thinking behaviors. Right? We're talking about the way your mind approaches fundamentally new problems. And really what we're talking about is the conservation of resources during the solution process. Right? In other words, in the Einstellung effect, the thing that is lost isn't the actual solution being correct or incorrect. It's how much work did it take to get there? How much harder is it to get to the problem? The problem's better. The problem's better. The problem's better. If we use the same thing that we've used in the past. So, an example of the Einstellung effect could be that you learned a new framework in order to solve a previous problem. So, in order to solve this problem, you will learn another new framework. This is an example of using extra resources where it's not necessarily the best place to use those resources, right? Just because learning a framework previously opened you up to the correct solution doesn't mean that learning a framework this time is going to open you up to the correct solution again. The same thing is true if you want to, for example, get a raise, right? Let's say that you're seeking a raise in your job and the last time you got a raise, you did X, Y, and Z. If you do X, Y, and Z again, that doesn't mean that you're going to get a raise again, right, the situation is different, the problem is different, and you should look at it from a brand new perspective. This is why this is such an important thing to understand. Our minds have a tendency to think that all things being equal, we can treat our problems very systematically, and usually we're going to fail at some really important piece of this, in particular, spending too much resources or arriving at the problem after a very long detour around a pre-preliminary problem. So, I told you that one thing did make a difference in Luchin's study, and hopefully that's what this episode is going to act as for you today. Luchin wrote the words, don't be blind, on some of the participants' secondary and tertiary problems, right? And for those people who he wrote the words, don't be blind, at the top of their paper that had the problems outlined on the paper, for those people that he wrote that message to, he saw a significantly better recovery rate from the Einstellung effect. In other words, people who saw a simple reminder, don't be blind, people who saw a simple message reminding them to think a little bit harder about this problem, when they saw that, they actually did that. So, let this episode be that reminder for you today, but in the future, you're not going to have this episode to listen to unless you go back and remind yourself of the Einstellung effect by re-listening to this episode in the future. That's perfectly fine as well, but you may need to set up some sort of systematic way to remind yourself when you go into problem-solving mode, when you encounter a new problem, this should become a habit to remind yourself very simply to treat this problem as a fundamentally new problem. Treat this as a new class of problems. Very often, what you will find is that even though your solution may look similar to a solution in the past, you're going to arrive at that solution with much better resource management. In other words, you're going to use less energy by simply using more of your brain earlier in that process. Hopefully, this has been an enlightening discussion on the Einstellung effect. I was lucky enough to receive a tip on that, and I hope you enjoyed it. I'll see you in the next episode. The Einstellung effect from a listener. If you want to send me something that you'd like for me to talk about on the show, if you want to send a question, just an idea or a story, I love getting all of your stories. You can send those to me by going to spec.fm slash Slack. You can join our Slack community. You can also send them to me directly at developertea at gmail.com, developertea at gmail.com. That email address has questions from hundreds of listeners at this point, and I'm so excited to connect with you all on a personal level. Very excited to get your stories and your questions there. Thank you so much for listening to today's episode of Developer Tea. Don't forget, if you are looking for a cloud Linux solution, a solid state drive in the cloud with two gigabytes of RAM for only $10 a month, and they're giving you $20 for free in credit just for being a Developer Tea listener, use the code DEVELOPERTEA2017 at checkout. Go to spec.fm slash Linode. Thank you again to Linode for sponsoring today's episode of Developer Tea. Until next time, enjoy your tea.