many listeners of developer t have probably heard of the marshmallow test the basic idea of the marshmallow test is to have a uh in in the test at least have a child sit down although i think i would probably struggle with this as an adult and set in front of them something that would give them immediate gratification marshmallows are a pretty good example of this you could do with a cookie or really anything with sugar and let them know that they can either have the marshmallow the single marshmallow now or they can wait for you to return and double their marshmallow treat now the interesting thing is that the return never happens the behavior of the children is documented and many of them fail they fail to wait many of them not only fail but choose to eat the marshmallow immediately and so the outcome from this and many other experiments after the marshmallow test all worked to reinforce the same basic premise people discount future gains this idea is called hyperbolic discounting and it's been studied many times over a dollar now is generally speaking more interesting than a dollar tomorrow but more insightfully a dollar now may be depending on your particular shape of discounting curve a dollar now may be more interesting to you than two dollars tomorrow but i want to take this concept and fill it out a little bit more and talk about how it might apply in our daily lives tonight when i finish recording this episode i have a plan to change the strings on my guitar actually have a couple of guitars and they all are in need of new strings if you don't know guitars over time the strings become a little bit less lively they're less enjoyable to play they're more likely to break but it happens progressively it happens slowly over time and so it's very easy to when that kind of degradation begins ignore it and so i'm going to show you how to do that and i'm going to show you how to do it in a little bit more detail but i'm going to show you how to do it in a little bit more detail to put it off there's other more important things than changing my guitar strings it seems in the moment like a low priority item and i can justify it by saying well the strings that i have still have some life left in them i'm going to keep playing the ones that i have but the truth is that every time i play on a degraded string i'm getting less of an experience out of playing my guitar of course there's probably some optimal degradation point at which now i should change the strings but almost every time i tend not to i tend to let it go until it is far beyond that point why is that well in another area you might find yourself not making your bed every day you may find yourself allowing trash to pile up on your desk or perhaps you are cleaner than the average person but you haven't taken care of your development environment maybe you have old crufty code laying around maybe you're like me and you have shortcuts that keep on running on your iphone that don't do anything useful anymore and you're not making your bed every day you may find yourself allowing trash to pile up on your desk you have a pile of reminders that you haven't cleared out of the backlog of your phone or pretty much everyone i know falls in this category you have thousands of emails that probably you'll never read and are not really useful to you but keep on nagging you with that red notification icon on your phone all of these things fall into a similar category these are items of disrepair in our work we see this and we often label it tech debt but there's also other types of work that might fall into this category things like automation things like improving your ide setting your personal development environment up setting up those uh key bindings actually taking the time to do that and then putting it into the work that you're doing and then putting it into the work that you're doing and then putting it into the work that you're doing and then putting it into the work that you're doing and then putting it into the work that you're doing to do the key bindings the way you like them these are all things that we put at the very bottom of our list why because we have much more important things to do tomorrow is my son's eighth birthday and in the morning i've already told myself tonight i'm going to make my bed why is that why would i take the time on my son's eighth birthday instead of spending the time with him why would i take the time to make my bed someone could easily say that that can't be the most important way to spend your time and therefore you should deprioritize that put it at the bottom of the list there may be days where that's the case but in this episode i hope to convince you that these tasks are indeed important not only because of the internal sense of pride that you might get for sticking to a particular commitment that you made although that has its own value but also because it changes the quality of the other things you do adding one more to the list hopefully this will provide a little bit of extra insight changing your air filter the reason why i decided to add this one at the end is to discuss this modifier quality of this kind of work if you changed your air filter now when will you benefit the intuitive answer is probably right now of course i'll benefit now because my air quality will improve the truth is that you're going to benefit now and as long as the air filter lasts and if you change the air filter again this is the interesting part there may be no change in the benefit this is why maintenance often goes unnoticed maintenance paradox when maintenance is being run properly when you are changing your filters when you're supposed to no one will notice the difference you won't notice the difference if i were to change my guitar strings every three weeks let's say that's a pretty aggressive strategy i may never notice any degradation on the strings at all and so the maintenance itself let's say it was performed by somebody else entirely without any of my knowledge i may never know that they're doing it it becomes invisible and so we don't get the same kind of gratification out of consistent maintenance this is kind of a reverse training or reverse incentive if you want to think about it that way because if we do wait until we can notice there is some kind of benefit to that action we get a training a sense of training that waiting and then performing the maintenance gives us a positive improvement we feel the change so these factors the fact that we have this tendency to discount whatever is not going to give us immediate gratification we tend to devalue that relative to other options that will give us immediate gratification that's going to provide friction to maintenance additionally in order to get into a good habit of maintenance you have to kind of deregulate yourself a little bit from the dopamine rush that happens if you don't keep up with your maintenance a good example of this is somebody who lets their closet get out of control i might know someone who does this on a cycle it's not my wife it's me i tend to allow my closet to pile up it's a bad habit that i have that i'd like to change the trouble is i tend to allow my closet to pile up and i tend to allow my closet to pile up that very often i end up training myself with a rush of dopamine once i've allowed my closet to pile up once i've thrown my shoes on the ground instead of putting them on the shelf enough times there is a sense of relief that comes whenever i finally do get around to cleaning it and so i have this bad cycle this is training me that it's okay that it's okay to let stuff sit on the floor because the marginal benefit the marginal benefit of cleaning it now of picking my shoes up immediately doesn't provide me enough of an immediate gratification and if i do allow it to pile up eventually i do get that larger reward so it's kind of a catch-22 this maintenance paradox but there's yet another force that makes maintenance difficult and this is a little bit of a newer theory in psychology it's called the construal level theory and it comes from a paper and i'm going to attempt to say these names i may say them incorrectly please forgive me if i do yakov trope and nira lieberman or lieberman wrote a paper about construal level theory of psychology and the basic idea presented in this paper is that we construe the connection of our actions for example we have a cognitive construal and construal kind of means that we're distancing ourselves there's different kinds of distances that they talk about specifically they talk about temporal distance that is distance in time they talk about spatial distance that is literal physical space they talk about social distance that is the things that i do don't affect me but rather they might affect someone else or or this action may affect someone uh in a in a social group and then finally hypothetical distance and each of these applies to this concept of maintenance we've already talked about the idea of ten temporal discounting which is uh a direct example of temporal distancing that is that because we have this temporal discounting that is um you know the the value happens sometime in the future right the the value of this action is disconnected from me or it is less valuable than something uh less immediate value than some other action right if i'm not doing something that's if i were to do maintenance then i'm not going to have the same immediate value as some other action i might take right um the temporal distance here it creates that uh or it's created by that discounting right so uh we're creating a little bit of distance between ourselves and the value that we feel from the action that we're taking similarly uh you know spatial distance is a little bit of a of a hard one to talk about with maintenance but we've all experienced this uh this feeling for example it's likely that areas that are further away in your house for example an attic or a basement are going to be in more disrepair uh than areas that are closer to you um and and that's not uh any difference necessarily in terms of ownership or whose space is it is just that it is much closer physically to you uh the the concept of social distance and i'm not talking about social distancing uh as we learned in during the covid era but social distance in this case would mean that the actions that we're taking let's say for example a maintenance action uh in in a code base that we're responsible for uh but that we are not necessarily going to keep being responsible for right and perhaps uh you know the the effect that our code has on another team there's going to be some distance there because we're not impacted directly or as directly as someone else says and then finally and perhaps most interest interestingly for maintenance is the hypothetical distance this one is especially uh profound for me and i think it's a very important one because it's a very important because this goes directly to the idea of preventing or a statistical effect if i were to change the strings on my guitar then i am preventing the experience of playing on dead strings this is what gives that feeling of uh of distance right it gives that maintenance paradox uh it creates that maintenance paradox that we never actually feel the distance because it's the hypothetical distance it is the hypothetical distance that we are preventing it's hard to know exactly how valuable a given bit of work will be because we never actually experienced the downside the prevention kept us from experiencing the downside so we can measure uh potentially we could measure what our hypothetical losses would have been had we not put that measure in place but very often the effort to measure hypothetical losses is not undertaken instead we measure our real losses that are happening in another area and so maintenance ends up being deprioritized while reactive work is not being prioritized and so we're going to keep going with this uh and i think this is a very important part of this uh this is a simple effect of visibility in this case it's much more visible when we have real losses rather than hypothetical losses and again this comes back to that construal theory uh right this this construal level theory that the hypothetical distance is going to be less present to us it's going to be less uh impactful less important and i think that's a very important part of this uh and i think that's a very important important to us. So all of these are friction to maintenance. What do we do about this? What do we do about all of these effects? Maintenance becomes a part of how you behave. Let me say this again. Maintenance becomes a standard practice, a standard operating practice in how you behave. So, you know, another way to think about this is it becomes habitual. It becomes habitual. Why am I making my bed in the morning tomorrow? Why am I making my bed in the morning tomorrow on my son's eighth birthday instead of immediately going to spend time with him? I'm going to get up and make my bed. It's because I will experience the important parts of my day differently. Right? Just, not just about the bed. It's about creating an environment for me that is calm and serene. Making my bed allows me to feel a sense of control. And there's a lot of other ways that you may apply this. And psychologically speaking, not all maintenance is going to have the same psychological effect, right? So this is for me personally, it will enhance the time that I do spend with my son. The quality of that time will be improved in the same way that if tomorrow afternoon during his birthday party, we're going to go swim in a swimming pool. I'm going to stop and put on sunscreen. This is a maintenance, a preventive measure. It's going to prevent future... Pain for me. I've had sunburns plenty of times in my life. I don't want to experience one tomorrow. And so instead of immediately jumping in and having fun, instead of, you know, getting right in the pool and later having to pay for, you know, how fast I wanted to get into the pool, I'm going to take the time and perform that basic maintenance as a matter of habit in order to... In order to... Deal with that hypothetical value. The hypothetical distance between the ideal experience, right? I'm going to prevent a burn. So the whole framework here, the idea is to help you understand that maintenance is unlikely to happen through our typical prioritization structures. It's very hard to convince our children that maintenance is unlikely to happen through our typical prioritization structures. Because of all of these different biases and things like the control level theory, the fact that we have this temporal discounting, you know, this hyperbolic temporal discounting, all of these things are friction to us performing these maintenance type duties. The kind of work that feels marginal. It feels low value in the moment. It feels low value in the moment. Very likely. likely if you were to pull out your Eisenhower matrix, and if you listen to the show, you know exactly what I'm talking about. If you are a new listener, go Google Eisenhower matrix. You've probably heard of it. This would fit squarely in the important but not urgent category. These kinds of tasks are important, but they are usually not urgent until they become urgent, until your strings break on stage, until your room is so messy, or until your bed has not been made for so long that you can't find the sheet, right? That the disrepair begins to become overwhelming. So I encourage you to adopt a maintenance mindset, adopt maintenance habits. Now, it's an exercise I'll leave up to you to determine to what degree. That is the balance that you have to use your own frameworks and wisdom and insight to determine. But it is unlikely to happen through a singular frame. You are unlikely to participate in these behaviors through basic prioritization structures. Thanks so much for listening to today's episode of Developer Tea. I appreciate you making time for this podcast today. This is unlikely to be the very most important thing that you'll do today, but I hope that this can act as somewhat of a maintenance behavior in your career and in your professional life and beyond. I very much appreciate the audience who listens to this show, the people, the engineers and software developers, the designers, everyone who listens to the show. You make it worthwhile to make this podcast each and every week. So thank you so much for listening. If you enjoyed this episode, two things I'm going to ask you to do. One, go and leave a review in iTunes, whatever podcasting provider you use probably has reviews. iTunes is the most impactful to the show's longevity, our ability to keep going as a podcast. And then second, subscribe in whatever podcasting app you're currently using. The last thing I want to say is that if you're a podcasting provider, you're going to have to invite you to join the Developer Tea Discord community. Come and check it out at developertea.com slash discord. That is free and it will always be free. Thanks so much for listening. And until next time, enjoy your tea.