In today's episode, I talk about turbulence, and a new approach to responding to difficulties you encounter. Developer Tea is proudly supported by Dev Bootcamp, the original immersive coding program that transforms beginners into full-stack web developers. Head over to devbootcamp.com/developertea to learn more.
In today's episode, I talk about turbulence, and a new approach to responding to difficulties you encounter.
Developer Tea is proudly supported by Dev Bootcamp, the original immersive coding program that transforms beginners into full-stack web developers. Head over to devbootcamp.com/developertea to learn more.
Please take a moment and subscribe and review the show! Click here to review Developer Tea in iTunes.
Hey, everyone, and welcome to Developer Tea. My name is Jonathan Cottrell. And in today's episode, I'm going to be talking to you about how to deal with turbulence. Today's episode is sponsored by Dev Bootcamp. Dev Bootcamp is a short-term immersive software development program that transforms those who are new to coding into job-ready full-stack web developers. We will talk a little bit more about Dev Bootcamp later on in today's episode. When I was young, my dad would take me and the rest of our family flying. He was the pilot. Dad has had a private pilot's license for longer than I've been alive. Now, you may expect that this is a child's dream scenario, getting to fly pretty much any time they wanted to. But the thing was, I was incredibly sensitive to turbulence. And I get pretty sick and perhaps, more importantly, easily frightened when we would fly. This was especially true whenever we flew over mountainous regions. One day, Dad explained to me how, as the airplane moved through the air, the air kind of treated the airplane like a river treats a stick that's floating downstream. If that river has a rock in it, the water flowing over the rock might rise a bit, then fall back down, go to the left or the right, fitting to the contour of the riverbed. He taught me this not because it would change the experience of the turbulence or somehow fix my intolerance. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. a developer, we happened upon a problem with a front-end view we were working on. We tried pushing some items into a set of arrays in the view, and we kept on hitting errors. We couldn't, for example, modify an array that was nested inside of another array. And instead, we had to modify the top-level array, and it got messy really fast. Anyway, the particulars aren't necessarily important. After about 30 minutes of googling and fixing one thing just to break another, we realized something profound, that if we did this particular data transformation elsewhere, more specifically, if we had done it not in our view, we could have been done practically moments after we started. It struck me shortly after that this wasn't a mistake in the design of the language. Instead, this was part of the design of this particular language, a view-templating syntax to be exact, that disallowed us from manipulating data to a significant extent. Now, why would a language be designed in this way? Why would it be designed in this way? Why would it be designed in this way? Why would it be designed to be harder to use? We'll talk about that after I discuss today's sponsor, DevBootCamp. Are you thinking about becoming a software developer? Check out DevBootCamp. DevBootCamp is a short-term, immersive software development program that transforms those who are new to coding into job-ready, full-stack web developers. Learn front- and back-end web development, teamwork, and leadership skills in a rigorous and inclusive environment. In just 19 weeks, you can join the DevBootCamp team. If you're new to coding, you can join the DevBootCamp team. Over 1,900 graduates and counting, DevBootCamp has several locations around the country and is accepting applications now. So visit devbootcamp.com slash developer T to learn more and let the folks at DevBootCamp know that you're a listener of developer T. Thanks so much to DevBootCamp for sponsoring today's episode. So we left off talking about the experience I had at work today, the front-end templating language that wouldn't allow me to manipulate, arrays of data I was working with. And this kind of thing happens a lot, doesn't it? You expect a language or a tool or perhaps even a person to behave a particular way and it or they simply won't cooperate. This could be a major point of frustration if you let it be. Or you can recognize that usually things are the way they are for a purpose, or at the very least, they are the way they are for a reason. In my particular case, with a friend of mine, I was working with a friend of mine who was bringing meijinijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijijij If you've worked in structures like MVC, you've likely heard the advice of separating your logic and your data from your view. As my coworker and I sat looking at the code, we realized that we were in some serious turbulence. I took a step back and asked, maybe this is how this is supposed to be. And so the code was rewritten and we floated down the river, moving through that turbulence and back onto our original course. We could accomplish what we wanted to accomplish because we responded to the turbulence, not by pushing against it, but by letting it guide us. I encourage you as you encounter things that push back against you, as you encounter turbulence, be it from code or from anything else, then instead of struggling against it, first ask the most important questions you can ask when you encounter a problem. Specifically, ask the question, why? It's very easy to assume that we know the answer to that question. As a young child, I assumed that turbulence ultimately meant something bad was happening, that that was the why of the turbulence. It was only after I understood, thanks to my dad's help, that turbulence was there for a reason that I could think differently and ultimately react to that turbulence with calmness. I hope you've enjoyed this episode of Developer Tea and this quick discussion. About turbulence and about allowing turbulence to guide you rather than you fighting against that turbulence. Once again, today's episode is sponsored by DevBootCamp. DevBootCamp is an immersive coding program that transforms beginners into full stack web developers. Head over to devbootcamp.com slash developer tea to learn more. Thank you again to DevBootCamp for sponsoring today's episode. And thank you for listening to Developer Tea. If you're enjoying the show, make sure you subscribe in whatever podcasting app. You use pretty much any podcasting app allows you to subscribe. And by the way, the Apple TV just now launched their podcasting app and the latest update to the Apple TV. So make sure you subscribe there as well. Thank you so much for listening. Until next time, enjoy your tea.