Detailed Notes
In this episode of Building Better Habits, Rob Broadhead and Michael Meloche delve into an essential skill for productivity—improving focus. Drawing from personal experiences and practical methodologies, they explore ways to enhance your attention span and align your efforts with meaningful outcomes. Here’s a recap of their discussion, peppered with insights to help you sharpen your focus and stay on track.
Read More: https://develpreneur.com/building-better-habits-improving-your-focus/
*Focus Challenge of the Week*
The hosts leave listeners with a practical challenge:
1. Create a daily to-do list. 2. Reflect on the “why” behind each item. 3. Regularly assess whether your efforts align with your goals.
By incorporating these habits, you can sharpen your focus, improve productivity, and avoid wasting time on distractions.
Improving focus is a skill that requires intention, practice, and self-awareness. Whether you’re tackling a software project or managing daily responsibilities, Rob and Michael’s strategies provide a solid foundation to enhance your productivity. As they remind us, the key is not to work harder but to work smarter—one habit at a time.
* Stay Connected: Join the Develpreneur Community*
We invite you to join our community and share your coding journey with us. Whether you’re a seasoned developer or just starting, there’s always room to learn and grow together. Contact us at [email protected] with your questions, feedback, or suggestions for future episodes. Together, let’s continue exploring the exciting world of software development.
*Additional Resources*
* Maintaining Focus At The Year End (https://develpreneur.com/maintaining-focus-at-the-year-end/) * Positive Focus – Victories and Tasks That Recharge Us (https://develpreneur.com/positive-focus-victories-and-tasks-that-recharge-us/) * Supercharge Your Focus and Productivity: Expert Tips for Success (https://develpreneur.com/supercharge-your-focus-and-productivity-expert-tips-for-success/) * Pomodoro Technique: Boost Your Focus and Productivity with Time-Blocking (https://develpreneur.com/pomodoro-technique-boost-your-focus-and-productivity-with-time-blocking/)
*Follow-us on:*
* https://develpreneur.com/ * https://www.youtube.com/channel/UCZOuFN_LhczvGyT2KSItH_g/featured * https://facebook.com/Develpreneur * https://twitter.com/develpreneur * http://linkedin.com/develpreneur
Transcript Text
[Music] morning so we are here we are back and we are trying to figure out what we're going to talk about I think you something in slack last time we had an extra there uh let's see so we had anti-habsburg did we do forget no that was more New Year see uh we had wrapping up your business in the New Year goals I think that might have been for the New Year's episode yeah that's all the New Year's stuff uh anti-habsburg so this is we've already talked about automating processes right y about automation let's see what do we got as we're stepping into the new year what is a good habit um well the focus in improvements I like um because I know we've talked about the um Pomodoro Technique list things of that but even with those and I guess we also talked about being present in meetings yep I think another one is um we'll see this sort of goes with Focus Improvement a little bit so it may be a good pairing is level [Music] your leveling Your Daily Grind basically because what I'm think about is like maybe some habits to help people so it's not so much feast or fam where it's like okay I'm having to like work all night and you know work 48 hours straight to get this thing done and then I'm done and then I'm sitting around and not I don't have anything to do and I'm twiddling my thumbs for a couple of days you know it's it's not as it's that kind of thing that's not as common now when you've got so many people have Sprints and stuff like that and smaller projects and smaller things but when you're doing you know 6 12 month 18 month projects it was very bad it's very difficult and those to be focused in the early ones cuz you're like I can take a day who's going to care and then you get to the last couple of months and it's like okay cancel canceling vacations and holidays and everybody's got to work seven days a week and some of that kind of crap that's maybe for ourselves finding ways to help that out so less highs and less lows sort of like more of a steady stream on your staying busy yeah so staying focused both of these are sort of time management stuff but yeah I think that's where you were going with the focus too because I think during the holidays we were all over the place even with trying to follow you know what we've talked about up to now but it's like trying to with yeah with Focus Improvement I thinking even within the task that we know we have is making sure that we're sort of like it is a little bit like that it's basically it's being present in whatever the task is that you're working on and not you drifting too much squirreling away or chasing rabbit down rabbit Trails oh I think we did talk about that one um a little bit because wasn't that also like the screen time in that trying to narrow your focus just well that was that was eliminating bad habits that's right okay yeah for those of you in the pre-show this is what happens we a lot of the things we talked about can cross over and become multiple conversations yeah chair a little higher so my knees aren't quite as cramped well let's start with a focus Improvement we'll see what happens if we we can start with that and see where it goes and then we'll come into the next one and we'll figure out what we want to go with that at least we have some ideas for it yeah that sounds good because I think the initial idea for pushing this to this week's uh podcast was because we the other two made more sense together in this one I think we thought we'd have something else to go with it to kind of pair up the week exactly so we'll see how that goes let me put my do not disturb to make sure that's not distracting me too much and we'll do our famous 3 two well hello and welcome back we are continuing our season where we're building better habits building better developers through those habits we are develop andur I am Rob Broadhead one of the founders of De develop andur which doesn't always off the tongue real well especially when I've only had like a few cups of coffee or tea actually is my drug of choice anyways already digressing so it is one of those days I guess this episode that we are going to talk about improving your focus so it's going to be perfect topic for this I want to introduce myself a little bit more I am also a found of RB Consulting where we are a boutique consulting firm we basically help you Wrangle your technology that's out there your needs and the technology you already have have so that technology sprawl that we tend to have just like you may have in your personal life you've got just too many devices and too many things you're looking at trying to make a find a way through simplification automation integration to just focus those things down so your technology is now your friend and your tool and not the thing that is sucking up all of your time also going to be some of those things going be helpful as we talk about the topic this episode as far as habits go really burning in the like the pomodora has continued to be just I cannot push that enough to say if you haven't gone go back to that was one of the early episodes basically walk through what a pomodora is we talked about doing just instead of trying to do them all day but just try to have a couple a day that are focused periods it has really helped me and it's also helped me uh with one of the E habits we talked about is basically doing stuff that's fun so the things that I really enjoy is giving a little bit of time to that uh and this is by doing things are fun it's the stuff that I enjoy and work and it's also touching some of the projects and some of the things that I need to do so that they don't just falter and disappear and the next thing you know it's you know you haven't touched that in six years and you forget where it was at so there's a lot of benefits in those in the habits um automation continues to be a good one I think it really is one of those that that's just like if you can get into that each week look at one or two even just one thing that you can automate that will build up and give you a nice Snowball Effect related to The Snowball Effect is my good and my bad the good well we'll start with the bad I guess is we just got pummeled by snow so we're pretty much snowed in right now it's like I don't know more than an inch which around here is too much snow because they don't have clearing cleaning other than the major roads major roads probably fine but getting to those a bit of a a challenge so that's I guess a bad thing but a good thing is is now that I'm snowed in for the weekend I get to catch up on a lot of the chores and tasks and stuff like that that was my ever building list of things that got pushed to tomorrow and then tomorrow and then tomorrow and tomorrow and coming out of a very busy holiday season probably a real good time to have you know take a couple of days and catch up on such things so that my mental health can actually improve as well somebody whose mental health is not improving at all right now because he's stressing out because I'm about to put him on the hot seat is my co-host Michael go ahead and introduce yourself hey everyone my name is Michael malash I'm one of the co-founders of developer ner building better developers and I'm also the founder of Envision QA where we our entire focus of our company is to bring test driven development to improve software development within companies be it's small business um mediumsized businesses healthc care to take your software that is potentially having problems or user experiences are buggy we help you streamline that whole process to make sure that when you write code build code it is tested and when it gets out to the users at the end experience they have a nice uh experience with the software no bugs no problems and with this process it also helped streamline development process so your developers aren't spending as much time tracking down bugs or missing bugs because they can push a button and know if the software Works before they even roll it out the door talking about good and bad uh good uh had a very productive week this week things are moving along on our project uh bad like Rob said we got snow in I think we got more snow than you guys uh we're up to about 8 in and I'm praying it melts tomorrow cuz we are going to the airport next week to so my wife can fly to California hopefully not deal with the fires but we'll see uh habits so I have been doing really good on some habits and really bad on others so the Pomodoro I started really good at the beginning of the year and I've kind of slipped I've gotten into uh some bad habits where I've been kind of heads down coding and the next thing I know I am five six hours in and I have not moved from my desk uh which also means I'm failing the taking breaks habit uh so I've kind of slipped a little bit but the good news of that is I actually got a lot done like I was so in the zone and really cranked stuff out downside I'm a little more burned out so uh getting back into some good habits which kind of worked into that was I was following some good list checklist uh I was more focused in meetings and I was actually really working on trying to plan things and schedule things the problem was I was so overbooked that it just I wasn't moving things forward so back to the habits of this week is trying to get back to the Pomodoro and taking breaks and kind of like Rob said getting to the point where we can spend time family and friends and doing things we want well that's what we're going to re going be part of the side effect I guess of what we're going to we cover this time what I want to talk about is we're going talk about habits related to essentially improving your focus and this is not just it is a little bit the general distractions that we've talked about whether it's your phone or your mail or some things like that but it's also it's really more along the lines of being busy versus being productive it is about figuring out what is it that you actually need to do for the things that you need to do it may seem like that's too many to-dos in a you know in a sentence but it really is it's we have tasks we have things that are our responsibilities and our assignments whether it's in personal life or more often and which is where we're going to really focus today is in the business in the whether it's our side hustle or our main hustle so we've got things like we will have you know tickets maybe that we're working on we will have a product that we're building or a design that we're creating or something along those lines and there is a lot of stuff we can do that is effectively busy work that is not terribly useful to us I mean it's yes it needs to be done maybe but sometimes even then it doesn't need to be done it could be pushed to a later date and then suddenly just sort of evaporates because we didn't need to deal with it now some people are sitting there out there may be saying yeah that's why we don't have to actually document designs and requirements because they're always going to change like wrong that is not it not talking about like eliminating everything that you don't like to do which is effectively documentation but it is making sure that what you do is productive and serving the goal that you have for example some people can write like let's say take a weekly status and over the years there are some developers that their weekly status is I wrote code okay not very helpful and so you actually in that case you sort of wasted your time even putting that down it's like you need to have something that is useful it's like hey I worked on this I worked on that here was a challenge here was something I overcome something that provides whatever level of insight is needed for that for that task that Weekly status task hopefully your manager customer whoever it is can help you refine that now sometimes overcommunication is not a bad thing but maybe in your status instead of I wrote code you have a breakdown of every hour like how many lines of code that you looked at and what you wrote and maybe some you've got like code Snippets and things like that that you've pulled into it while yes that thoroughly documents what you did nobody cares it's it's one of those that it's like you're adding documentation that's not needed it's the same idea is if you generate a report to somebody and it's got a million records in it it is too much nobody's going to look through a million records of data you need to keep why in Focus so if you're you know if you're building a product and you're going to show thousands and thousands of Records in a report then instead of yes maybe you can spend your time and now you've built that report and you can check that off and that's a function or a feature that you can say like hey we can do that maybe take a look at that and instead of doing that figure out what is the actual goal what is your what are you trying to serve your customer with with that report and then maybe you need to make adjustments a lot of times it's things like maybe it's a summary or maybe it's just an exception report or something along those lines and those are I mean we've learned some of that like exception reporting is sort of an industry standard nobody cares if you process a million records successfully nobody wants an email that says I processed record one two 3 four they may want to say yes I processed a million records but that's one you know one value that's not a million values or words that's one one ping to your phone not a million pings to your phone that everything's going well because if you have everything going well and then somewhere in there it went wrong you've got too much information so that's where we want to focus we want to focus on the why and that's I think the easiest part that's sort of the easiest way to describe what we're going to have in the challenge this week is how do we get to the why how do we figure out build some habits that will help us do the right thing do the valuable thing and how do we avoid going down those rabbit trails that we sometimes do how do we avoid losing a day tweaking a color on a website that when the color is just for us and it doesn't matter to somebody else I mean there's things like that I know we've all done and we come back and we're like wow I spent a lot of time on that and it really is going to come back to was that time valuable was it time well spent and so before I go into the challenge a week I'm going to throw this over to micro and get your thoughts on all this yeah so it's rather interesting uh our conversation today you know improving our Focus you know explain the why uh very interestingly a task that was given me this week was I was handed a project from another team with literally no guidance other than here's some documentation and all we're expecting you to do is just stand up the code what we don't know or what we don't have access to is we don't have access to the previous developers so we have teams that are working with this product but no one knows how to stand up this product so we are literally blind and kind of going into this like oh how the heck do we do this and that is a bad practice because really you know you want your focus to be handoff software have another team come in pick up the software and hit the ground running you don't want to essentially hit a roadblock like that so to me a lot of times when you're focusing on your why or like focusing on you know what it is that we're doing to stay productive you kind of have to look at what you're doing like you said um make sure that the tasks you have can be productive um make sure that the stuff that you're working on ask yourself you know like you said is this moving the ball forward you know you don't want to spend a day working on a color but if the if your task is to build a dashboard you do need to make sure that some functionality and features of that dashboard work you know you want to make sure that the user inputs are there you know that is important the look and feel may be not as important at the beginning because what you want to do is you want to make sure that the feature is functionally complete and then you can come back later and add all the bells and whistles and make it look good now there is a caveat to that because you know yes sometimes look and feel may not be important but those actions those controls are however you don't want to spend like Rob mentioned you don't want to spend days on a drop down list to make it like cross functional make it you know look all nice and pretty but you do still need to make sure that it meets the requirements of the user so it kind of our why kind of goes back to those requirements or maybe lack of requirements is what is it that they want how do they want it implemented could be Loosely interpreted but essentially what you need to do is you need to make sure that you get it functionally complete that hey this works the way it's intended and then kind of move on from there you can come back and apply Focus later interestingly enough that can also flow to those status uh emails or the end of the week status updates like Rob was talking about because as you're building something as you're working on your tickets yes you're writing code but you're working on requirements you're working on functionality and features so when you go to write those status updates depending upon who your audience is yes it can be very technical however if you're dealing with customers nine out of 10 times they don't care about the technical they care about that functionality they care about the requirements what is it that you're doing that is giving them quality or the quality of the code what is it that you're doing to the code that they will see that they will understand so you need to make sure you you essentially can talk to that functionality hey I was working on building you this uh dashboard for this functionality within that dashboard these are the features I worked on this week you don't have to get real technical with the code but you might want to specify though or highlight features that may be featured complete or are still in progress so as you're working on your why as you're working on your focus think about these things and also think to make sure that you're working to get to that feature complete not oh this is a nice Bell and whistle hey look I did something no 9 out of 10 times what we do as developers is never seen by the end user they just see software that works and that is all they care about so be careful trying to show off and make sure that you show up and make sure that your software delivers what you're trying to do and that's really like the focus is that there is a I think we over we exaggerate how impressive our software is to people uh to our end user there are a lot of most often your end user is going to be impressed when the software works if you've got like a nice little you know Spinning Wheel that shows up at certain times or you've got a certain color that's just like been you know scientifically proven to be soothing or whatever it is and there's all these things that we do that we don't necessarily need to do that we're actually in a sense we are actually being bad stewards of our our time of what our customer is paying us to do or our boss or employer is paying us to do CU they're paying us to solve problems s mostly now you may be in a situation where the problem you're solving is a marketing problem so it you have to appeal so but that's then the focus the design the the pop or whatever it is the call the action then sometimes it is very valuable to spend that time because that is your goal that is what you want so in that case maybe the content and the presentation are number one if you're at the top of a funnel but when you get to the end of the funnel and you you're giving a product that somebody's purchased then it's like you need to you walk through that funnel you built up that story you built up all those valuable the value proposition so you now have to deliver on the value proposition at this point the value proposition is not spoken mirrors it is not prettiness it is nailing the requirements that you have laid out for the customer and with any product that's what it is for example you can look at spreadsheets are great that's a good example of this because really what you want with a spreadsheet is you want to be able to take a bunch of numbers and stuff and present them in a way that you can see a lot of information at once and then you can do a lot of Wheeling and dealing with it you can do calculations all this kind of stuff you don't need generally speaking you don't need like really pretty cells and stuff like that you just need a grid and you need the ability to put as much crap on the screen at a time as you can basically is you know so it's it's very functional it's very specific and its function and a lot of what we do I think we over complicate and think that we should provide more than we should so that's where I want to get to this is it's it's really it is you know busy versus productive which really comes down to is this is this functional or is it pretty am I you know essentially just trying to present this in a better light than it is or am I trying to make it better so I could you know the goal would be that even if it's the ugliest presentation the functionality is so good that it's still compelling but then pretty it up as well now one of the wasted time things is um is what Michael sort of touched on is the idea that like get the functional first you can throw something out there that's visually okay you know it doesn't you don't want people to like you know oh my eyes are burning after they see your interface but they don't need to be like they don't need to go and like say I have to go smoke a cigarette after seeing the you know your your interface either because the functional thing needs to be complete you're going to you may add buttons you may remove buttons you may add fields and remove Fields you may move fields around you may have uh validations and communication of some sort like notifications and messages and all this kind of stuff that's all going to be part of completing the functionality now maybe you know exactly what it's going to look like from the start so you can do all those things at once but normally that's not the case because there's going to be things that we're going to get into that is an unknown and now we've implemented the functionality it's like oh yeah that's right we need to do this differently or we need to change that and that means what anything that you changed it if you spent time beforehand pting it up and trying to make it Pixel Perfect then you've probably wasted your time because now everything else around it maybe has changed and so this again it comes down to what you know knowing where the value is and that's the habit I want to I want to sort of look at that's a challenge is this is much like taking a break it is on a given day because we've already we're building lists we're doing all these things is maybe look at what's on your to-do list for today you know or tomorrow when you're putting your list together and with that when you put your list items on there think a little bit about what does it mean to check that off what do I need to do to check that off what I what is the goal of that thing what is the why for that checklist item because I can be working on that checklist item all day and maybe not make a lot of progress until the last 5 minutes and then it's like boom I'm done so you just wasted all day minus the 5 minutes so that's what you want to look at is it's sort of like Performance Tuning your to-do list maybe that'll be the title of the the podcast that's actually pretty cool idea um but it's really it's looking at your to-do list and saying what is the essentially what is the most efficient way for me to get this thing done it's a little bit of design work on your to-do list before you get into doing your to-do items it's think about how am I going to approach this how am I going to work with this and this is something that actually you can actually benefit from as well the idea of like maybe there's some ordering to that to-do list maybe we've talked about like batching things together and things like that so maybe it makes sense to do these three tasks and then these other three tasks because they are very familiar or it may make sense to do this task and do this very different task because it allows you to switch gears it forces you to take a little bit of a break so think about your why on your to-do list and that's what I want you to do is for the next week there as a challenge is every day when you build your to-do list before you dive into it take just a couple of minutes and think about each of those items maybe you add another level detail to your list or some notes or something like that to remind you what is it that I really need to accomplish to get this done and then at any time during the day if you're sitting there and you're just like I'm heads down and I'm cranking through stuff maybe periodically or put a reminder alert or something like to say am I actually doing the things I need to do and this I think will help you with some of the other things we've talked about like meetings and if you're walking around the office and people start talking to you and you just get sucked into you know water cooler talk or whatever because you can say wait a minute I got to get back and do this thing I think it's going to help you stay focused it's going to help you first personally to avoid rabbit Trails but then also when you're dealing with other people and I want to throw that to you Michael give you sort of the last word on this yeah so it's I kind of like where you went with that so the other thing with that is you know don't be busy be productive you know don't be the person running around the office with your cell phone on making it look like you're busy you're talking to someone be at your desk be present get your work done stay focused and you're going to see probably an improvement in productivity and a decrease in uh distractions so one of the things that's very productive that you can do right now is write us an email send us an email at info@ develop ur.com you can also contact us out on Facebook at the developer Nur site you can check us out on developer.com there's contact forms there you can provide comment comments and feedback on any of our content that's out there which is literally over thousands of Articles out there between podcasts and videos and blog articles and all kinds of stuff wide range of technologies that we cover uh everything for beginning developers and there's even some more advanced Topics in there as well love for you to check that out you can also find a lot of the video stuff amazingly enough out on YouTube we've got lots of stuff there on the development or channel uh old Mentor sessions and presentations of varing sorts and then a lot of these you may even be there hello to all of you that in the YouTube audience uh because we also do the podcast uh we have a video version of that as well every uh actually every couple of days when we put these things out feel free to also leave us feedback on wherever you listen to podcast because there's so many of those out there the Pod catchers that are out there uh would love to get feedback from you whe good or bad we just want feedback because we want to know how we can serve you better We Want To Build The Better developers but we're also building a better podcast in doing so at least that's our goal that's our why so now I'm going to let you to continue your productive day go out there and have yourself a great day a great week and we will talk to you next time bonus material so I was thinking through this one um it kind of bleeds into some of the other podcasts as far as the bonus stuff but again as you're going through your daily processes as you're trying to figure out your why you know write those lists make sure you keep track of what it is you're supposed to be doing uh so that you can kind of check off and go okay yes I was trying I need to get this done I need to get this done but also as you're looking at those lists and you're making those checks make sure that you're Focus focus is on what it is and that you're staying within the scope of your task so you don't essentially have scope creep like we talked about where you get stuck on a low button adding all that functionality and feature stick to the scope of what your task is meant to be if your scope if your task is too broad yes you're going to run into that issue where your focus is going to be jumping all over the place look at your task break it down redefine it and make that that scope I me I think in testing terms if then there should be a oneway path to get to the end of your task now how you get to that path maybe chopping down trees maybe getting on the interstate but how you get there is the journey but you have to Define your starting point and then Define your destination and then your focus and your scope is going to be to get from A to B you shouldn't have a to B to C to D to D back to B it should be straight A to B that's I like the the path analogy because I'm thinking about that just as something that that may help you guys out there and gals is think about making if you're going through you know a heavily forested area or something like that and you're trying to hack your way and make a path well the goal is to have a path through there the goal is not to have necessarily a pretty path so if you're if you're whacking away at the big things and clearing out a a way through so people can walk through it then you are being productive if you're going through and you're like trimming the sides of the flower so it's far enough out and you know there's not like one branch out of place or something like that then you're probably not serving the greater purpose and while that may be useful to some extent and you can argue that like well somebody could get hurt that little Branch could whack them and they could draw blood and they could die from bleeding to death or something like we can we can find ways to argue the importance of our stuff but honestly if we're arguing that there's importance to it even with ourselves and it's probably not that important and it's like it's really that argument should be should I do it at all then you can have that longer argument of yes it's at least worth it to some point come back to it but if you're arguing right now whether there's important enough to do it today then you probably should just pass on that the bonus thing I want to talk about is really timeliness of getting stuff done because that's we we touched on it a little bit through the episode but I really want to go back to that cuz when you think of what is now sort of a has become a big thing like the just in time delivery just in time fulfillment and it's really that's what scrum and agile is about when we talk about development is it's about doing it when it needs to be done and not doing it sooner and not doing it later and so this is where especially we talk about like maybe visual design and functionality and things like that and this is where particularly we're I think it helps us when we're designing software this a little bit one of those Advanced Techniques or whatever is that you you can look at the big picture like what am I what's the problem I'm solving what are the the steps to solve that problem and then looking at those steps is there commonality Michael mentioned the idea of like components and things like that so maybe you've got a solution that's got a bunch of dropdowns and maybe it makes sense to just each time you do that build your drop down and do your little list but maybe in looking at it it is worth it it is a worthwhile investment to instead say I have to do this 10 different times and instead of doing it in a larger sense and you know having a lot of work 10 different times I can do it once and then plug a couple of things in so it's a talks about the idea we're think about like code reuse and things like that so looking at the big picture and then find the way and this is sort of to prioritize is first there's the things that we're going to use a lot which goes to sometimes why there's struggle early on and you know we're building a product because we're really building a framework of some sort it may not be a full-blown framework but it's essentially the framework for this solution for this product for this application and so we're building these pieces and it's things like you know it is it's the general looking feel and some things like that that we're going to spend a little bit of time we're going to put that there so now we have placeholders for the features that we're going to build later and so we need to think about am I building something right now that I'm going to actually replace with a general solution later or am I building something this is when it's done it's going to be done and that's sort of the follow-up to that is is understanding and it goes back to the challenge of the week is it's understanding what does done mean what does complete mean for this list item for this thing that's on my task and if I do that I think that will help me I know it helps me and I'm hoping it will help you I in the global sense hopefully when you're doing that it will help you maintain that focus and so like Michael said it's one of those when you say I'm going to work on this task you know that this is where I'm at and because you know what the goal of that task what is completion for that task then you can make sure you're focused on getting to completion and anything that takes you off of that path you can rain yourself back in and get to the completion of your task that being said we have gone a little bit I guess not too long but little over on this one mostly because we were trying to figure out what the heck we're going to talk about and I think it did turn out pretty good so stick around because we'll probably do this again in the very near future that being said go out there and help yourself a great day I'm going to go have some more tea because I'm not caffeinated enough and we will talk to you next time [Music]
Transcript Segments
[Music]
morning so we are
here we are back and we are trying to
figure out what we're going to talk
about I think you something in slack
last time we had an extra there uh let's
see so we had anti-habsburg
did we do
forget no that was more New Year
see uh we had wrapping up your business
in the New Year goals I think that might
have been for the New Year's episode
yeah that's all the New Year's stuff uh
anti-habsburg
so this
is we've already talked about automating
processes right y about
automation let's see what do we got as
we're stepping into the new year what is
a good habit
um well the focus in improvements I like
um because I know we've talked about the
um Pomodoro Technique list things of
that but even with
those and I guess we also talked about
being present in
meetings
yep I think another one is
um we'll see this sort of goes with
Focus Improvement a little bit so it may
be a good pairing is level
[Music]
your leveling
Your Daily Grind basically because what
I'm think about is like maybe some
habits to help people so it's not so
much feast or fam where it's like okay
I'm having to like work all night and
you know work 48 hours straight to get
this thing done and then I'm done and
then I'm sitting around and not I don't
have anything to do and I'm twiddling my
thumbs for a couple of days you know
it's it's not as it's that kind of thing
that's not as common now when you've got
so many people have Sprints and stuff
like that and smaller projects and
smaller things but when you're doing you
know 6 12 month 18 month projects it was
very bad it's very difficult and those
to be focused in the early ones cuz
you're like I can take a day who's going
to care and then you get to the last
couple of months and it's like okay
cancel canceling vacations and holidays
and everybody's got to work seven days a
week and some of that kind of crap
that's maybe for ourselves finding ways
to help that
out so less highs and less lows sort of
like more of a steady stream on
your staying busy yeah so staying
focused both of these are sort of time
management stuff but yeah I think that's
where you were going with the focus too
because I think during the holidays we
were all over the place even with trying
to
follow you know what we've talked about
up to now but it's like trying to with
yeah with Focus Improvement I thinking
even within the task that we know we
have is making sure that
we're sort of like it is a little bit
like that it's basically it's being
present in whatever the task is that
you're working
on and
not you drifting too much squirreling
away or chasing rabbit down rabbit
Trails oh I think we did talk about that
one um a little bit because wasn't that
also like the screen time in that trying
to narrow your focus
just well that was that was eliminating
bad habits that's right
okay yeah for those of you in the
pre-show this is what happens we a lot
of the things we talked about can cross
over and become multiple
conversations yeah
chair a little higher so my knees aren't
quite as cramped well let's start with a
focus Improvement we'll see what happens
if we we can start with that and see
where it goes and then we'll come into
the next one and we'll figure out what
we want to go with that at least we have
some ideas for it yeah that sounds good
because I think the initial idea for
pushing this to this week's uh podcast
was because we the other two made more
sense together in this one I think we
thought we'd have something else to go
with it to kind of pair up the
week exactly so we'll see how that goes
let me put my do not disturb to make
sure that's not distracting me too
much and we'll do our famous 3
two well hello and welcome back we are
continuing our season where we're
building better habits building better
developers through those habits we are
develop andur I am Rob Broadhead one of
the founders of De develop andur which
doesn't always off the tongue real well
especially when I've only had like a few
cups of coffee or tea actually is my
drug of
choice anyways already digressing so it
is one of those days I guess this
episode that we are going to talk about
improving your focus so it's going to be
perfect topic for this I want to
introduce myself a little bit more I am
also a found of RB Consulting where we
are a boutique consulting firm we
basically help you Wrangle your
technology that's out there your needs
and the technology you already have have
so that technology sprawl that we tend
to have just like you may have in your
personal life you've got just too many
devices and too many things you're
looking at trying to make a find a way
through simplification automation
integration to just focus those things
down so your technology is now your
friend and your tool and not the thing
that is sucking up all of your time also
going to be some of those things going
be helpful as we talk about the topic
this episode as far as habits go really
burning in the like the pomodora has
continued to be just I cannot push that
enough to say if you haven't gone go
back to that was one of the early
episodes basically walk through what a
pomodora is we talked about doing just
instead of trying to do them all day but
just try to have a couple a day that are
focused periods it has really helped me
and it's also helped me uh with one of
the E habits we talked about is
basically doing stuff that's fun so the
things that I really enjoy is giving a
little bit of time to that uh and this
is by doing things are fun it's the
stuff that I enjoy and
work and it's also touching some of the
projects and some of the things that I
need to do so that they don't just
falter and disappear and the next thing
you know it's you know you haven't
touched that in six years and you forget
where it was at so there's a lot of
benefits in those in the habits um
automation continues to be a good one I
think it really is one of those that
that's just like if you can get into
that each week look at one or two even
just one thing that you can automate
that will build up and give you a nice
Snowball Effect related to The Snowball
Effect is my good and my bad the good
well we'll start with the bad I guess is
we just got pummeled by snow so we're
pretty much snowed in right now it's
like I don't know more than an inch
which around here is too much snow
because they don't have clearing
cleaning other than the major roads
major roads probably fine but getting to
those a bit of a a challenge so that's I
guess a bad thing but a good thing is is
now that I'm snowed in for the weekend I
get to catch up on a lot of the chores
and tasks and stuff like that that was
my ever building list of things that got
pushed to tomorrow and then tomorrow and
then tomorrow and tomorrow and coming
out of a very busy holiday season
probably a real good time to have you
know take a couple of days and catch up
on such things so that my mental health
can actually improve as well somebody
whose mental health is not improving at
all right now because he's stressing out
because I'm about to put him on the hot
seat is my co-host Michael go ahead and
introduce yourself hey everyone my name
is Michael malash I'm one of the
co-founders of developer ner building
better developers and I'm also the
founder of Envision QA where we
our entire focus of our company is to
bring test driven development to improve
software development within companies be
it's small business um mediumsized
businesses healthc care to take your
software that is potentially having
problems or user experiences are buggy
we help you streamline that whole
process to make sure that when you write
code build code it is tested and when it
gets out to the users at the end
experience they have a nice uh
experience with the software no bugs no
problems and with this process it also
helped streamline development process so
your developers aren't spending as much
time tracking down bugs or missing bugs
because they can push a button and know
if the software Works before they even
roll it out the
door talking about good and bad uh good
uh had a very productive week this week
things are moving along on our project
uh bad like Rob said we got snow in I
think we got more snow than you guys uh
we're up to about 8 in and I'm praying
it melts tomorrow cuz we are going to
the airport next week to so my wife can
fly to California hopefully not deal
with the fires but we'll see uh habits
so I have been doing really good on some
habits and really bad on others so the
Pomodoro I started really good at the
beginning of the year and I've kind of
slipped I've gotten into
uh some bad habits where I've been kind
of heads down coding and the next thing
I know I am five six hours in and I have
not moved from my desk uh which also
means I'm failing the taking breaks
habit uh
so I've kind of slipped a little bit but
the good news of that is I actually got
a lot done like I was so in the zone and
really cranked stuff out downside I'm a
little more burned out so uh getting
back into some good habits which kind of
worked into that was I was following
some good list checklist uh I was more
focused in meetings and I was actually
really working on trying to plan things
and schedule things the problem was I
was so overbooked that it just I wasn't
moving things forward so back to the
habits of this week is trying to get
back to the Pomodoro and taking breaks
and kind of like Rob said getting to the
point where we can spend time family and
friends and doing things we
want well that's what we're going to re
going be part of the side effect I guess
of what we're going to we cover this
time what I want to talk about is we're
going talk about habits related to
essentially improving your focus and
this is not just it is a little bit the
general distractions that we've talked
about whether it's your phone or your
mail or some things like that but it's
also it's really more along the lines of
being busy versus being productive it is
about figuring out what is it that you
actually need to do for the things that
you need to do it may seem like that's
too many to-dos in a you know in a
sentence but it really is it's we have
tasks we have things that are our
responsibilities and our assignments
whether it's in personal life or more
often and which is where we're going to
really focus today is in the business in
the whether it's our side hustle or our
main hustle so we've got things like we
will have you know tickets maybe that
we're working on we will have a product
that we're building or a design that
we're creating or something along those
lines and there is a lot of stuff we can
do that is effectively busy work that is
not terribly useful to us I mean it's
yes it needs to be done maybe but
sometimes even then it doesn't need to
be done it could be pushed to a later
date and then suddenly just sort of
evaporates because we didn't need to
deal with it now some people are sitting
there out there may be saying yeah
that's why we don't have to actually
document designs and requirements
because they're always going to change
like wrong that is not it not talking
about like eliminating everything that
you don't like to do which is
effectively documentation but it is
making sure that what you do is
productive and serving the goal that you
have for
example some people can write like let's
say take a weekly status and over the
years there are some developers that
their weekly status is I wrote code okay
not very helpful and so you actually in
that case you sort of wasted your time
even putting that down it's like you
need to have something that is useful
it's like hey I worked on this I worked
on that here was a challenge here was
something I overcome something that
provides whatever level of insight is
needed for that for that task that
Weekly status task hopefully your
manager customer whoever it is can help
you refine that now sometimes
overcommunication is not a bad thing but
maybe in your status instead of I wrote
code you have a breakdown of every hour
like how many lines of code that you
looked at and what you wrote and maybe
some you've got like code Snippets and
things like that that you've pulled into
it while yes that thoroughly documents
what you did nobody cares it's it's one
of those that it's like you're adding
documentation that's not needed it's the
same idea is if you generate a report to
somebody and it's got a million records
in it it is too much nobody's going to
look through a million records of data
you need to keep why in Focus so if
you're you know if you're building a
product and you're going to
show thousands and thousands of Records
in a report then instead of yes maybe
you can spend your time and now you've
built that report and you can check that
off and that's a function or a feature
that you can say like hey we can do that
maybe take a look at that and instead of
doing that figure out what is the actual
goal what is your what are you trying to
serve your customer with with that
report and then maybe you need to make
adjustments a lot of times it's things
like maybe it's a summary or maybe it's
just an exception report or something
along those lines and those are I mean
we've learned some of that like
exception reporting is sort of an
industry standard nobody cares if you
process a million records successfully
nobody wants an email that says I
processed record one two 3 four they may
want to say yes I processed a million
records but that's one you know one
value that's not a million values or
words that's one one ping to your phone
not a million pings to your phone that
everything's going well because if you
have everything going well and then
somewhere in there it went wrong you've
got too much information so that's where
we want to focus we want to focus on the
why and that's I think the easiest part
that's sort of the easiest way to
describe what we're going to have in the
challenge this week is how do we get to
the why how do we figure out build some
habits that will help us do the right
thing do the valuable thing
and how do we avoid going down those
rabbit trails that we sometimes do how
do we avoid losing a day tweaking a
color on a website that when the color
is just for us and it doesn't matter to
somebody else I mean there's things like
that I know we've all done and we come
back and we're like wow I spent a lot of
time on that and it really is going to
come back to was that time valuable was
it time well spent and so before I go
into the challenge a week I'm going to
throw this over to micro and get your
thoughts on all this
yeah so it's rather interesting uh our
conversation today you know improving
our Focus you know explain the why uh
very
interestingly a task that was given me
this week was I was handed a project
from another team with literally no
guidance other than here's some
documentation and all we're expecting
you to do is just stand up the
code what we don't know or what we don't
have access to is we don't have access
to the previous developers so we have
teams that are working with this product
but no one knows how to stand up this
product so we are literally blind and
kind of going into this like oh how the
heck do we do this and that is a
bad practice because really you know you
want your focus to be handoff software
have another team come in pick up the
software and hit the ground running you
don't want to essentially hit a
roadblock like that so to me a lot of
times when you're focusing on your why
or like focusing on you know what it is
that we're doing to stay
productive you kind of have to look at
what you're doing like you said um make
sure that the tasks you
have can be productive um make sure that
the stuff that you're working
on ask yourself you know like you said
is this moving the ball forward you know
you don't want to spend a day working on
a color but if the if your task is to
build a dashboard you do need to make
sure that some functionality and
features of that dashboard work you know
you want to make sure that the user
inputs are there you know that is
important the look and feel may be not
as important at the beginning because
what you want to do is you want to make
sure that the feature is functionally
complete and then you can come back
later and add all the bells and whistles
and make it look good now there is a
caveat to that because you know yes
sometimes look and feel may not be
important but those actions those
controls
are however you don't want to spend like
Rob mentioned you don't want to spend
days on a drop down list to make it like
cross functional make it you know look
all nice and pretty but you do still
need to make sure that it meets the
requirements of the user so it kind of
our why kind of goes back to those
requirements or maybe lack of
requirements is what is it that they
want how do they want it implemented
could be Loosely interpreted but
essentially what you need to do is you
need to make sure that you get it
functionally complete that hey this
works the way it's intended and then
kind of move on from there you can come
back and apply Focus later interestingly
enough that can also flow to those
status uh emails or the end of the week
status updates like Rob was talking
about because as you're building
something as you're working on your
tickets yes you're writing code but
you're working on requirements you're
working on functionality and features so
when you go to write those status
updates depending upon who your audience
is yes it can be very technical however
if you're dealing with customers nine
out of 10 times they don't care about
the technical they care about that
functionality they care about the
requirements what is it that you're
doing that is giving them quality or the
quality of the code what is it that
you're doing to the code that they will
see that they will understand so you
need to make sure you you essentially
can talk to that functionality hey I was
working on building you this uh
dashboard for this functionality within
that dashboard these are the features I
worked on this week you don't have to
get real technical with the code but you
might
want to specify though or highlight
features that may be featured complete
or are still in progress so as you're
working on your why as you're working on
your focus think about these things and
also think to make sure that you're
working to get to that feature complete
not oh this is a nice Bell and whistle
hey look I did something no 9 out of 10
times what we do as developers is never
seen by the end user they just see
software that works and that is all they
care about so be careful trying to show
off and make sure that you show up and
make sure that your software delivers
what you're trying to
do and that's really like the focus is
that there is a I think we over we
exaggerate how impressive our software
is to people uh to our end user there
are a lot of most often your end user is
going to be impressed when the software
works if you've got like a nice little
you know Spinning Wheel that shows up at
certain times or you've got a certain
color that's just like been you know
scientifically proven to be soothing or
whatever it is and there's all these
things that we do that we don't
necessarily need to do that we're
actually in a sense we are actually
being bad stewards of our our time of
what our customer is paying us to do or
our boss or employer is paying us to do
CU they're paying us to solve problems s
mostly now you may be in a situation
where the problem you're solving is a
marketing problem so it you have to
appeal so but that's then the focus the
design the the pop or whatever it is the
call the action then sometimes it is
very valuable to spend that time because
that is your goal that is what you want
so in that case maybe the content and
the presentation are number one if
you're at the top of a funnel but when
you get to the end of the funnel and you
you're giving a product that somebody's
purchased then it's like you need to you
walk through that funnel you built up
that story you built up all those
valuable the value proposition so you
now have to deliver on the value
proposition at this point the value
proposition is not spoken mirrors it is
not prettiness it is nailing the
requirements that you have laid out for
the customer and with any product that's
what it is for example you can look at
spreadsheets are great that's a good
example of this because really what you
want with a spreadsheet is you want to
be able to take a bunch of numbers and
stuff and present them in a way that you
can see a lot of information at once and
then you can do a lot of Wheeling and
dealing with it you can do calculations
all this kind of stuff you don't need
generally speaking you don't need like
really pretty cells and stuff like that
you just need a grid and you need the
ability to put as much crap on the
screen at a time as you can basically is
you know so it's it's very functional
it's very specific and its function and
a lot of what we do I think we over
complicate and think that we should
provide more than we should so that's
where I want to get to this is it's it's
really it is you know busy versus
productive which really comes down to is
this is this functional or is it pretty
am I you know essentially just trying to
present this in a better light than it
is or am I trying to make it better so I
could you know the goal would be that
even if it's the ugliest presentation
the functionality is so good that it's
still compelling but then pretty it up
as well now one of the wasted time
things is um is what Michael sort of
touched on is the idea that like get the
functional first you can throw something
out there that's visually okay you know
it doesn't you don't want people to like
you know oh my eyes are burning after
they see your interface but they don't
need to be like they don't need to go
and like say I have to go smoke a
cigarette after seeing the you know your
your interface either because the
functional thing needs to be complete
you're going to you may add buttons you
may remove buttons you may add fields
and remove Fields you may move fields
around you may have uh validations and
communication of some sort like
notifications and messages and all this
kind of stuff that's all going to be
part of completing the functionality now
maybe you know exactly what it's going
to look like from the start so you can
do all those things at once but normally
that's not the case because there's
going to be things that we're going to
get into that is an unknown and now
we've implemented the functionality it's
like oh yeah that's right we need to do
this differently or we need to change
that and that means what anything that
you changed it if you spent time
beforehand pting it up and trying to
make it Pixel Perfect then you've
probably wasted your time because now
everything else around it maybe has
changed and so this again it comes down
to what you know knowing where the value
is and that's the habit I want to I want
to sort of look at that's a challenge is
this is much like taking a break
it is on a given day because we've
already we're building lists we're doing
all these things is maybe look at what's
on your to-do list for today you know or
tomorrow when you're putting your list
together and with that when you put your
list items on there think a little bit
about what does it mean to check that
off what do I need to do to check that
off what I what is the goal of that
thing what is the why for that checklist
item because I can be working on that
checklist item all day and maybe not
make a lot of progress until the last 5
minutes and then it's like boom I'm done
so you just wasted all day minus the 5
minutes so that's what you want to look
at is it's sort of like Performance
Tuning your to-do list maybe that'll be
the title of the the podcast that's
actually pretty cool idea um but it's
really it's looking at your to-do list
and saying what is the essentially what
is the most efficient way for me to get
this thing done it's a little bit of
design work on your to-do list before
you get into doing your to-do items it's
think about how am I going to approach
this how am I going to work with this
and this is something that actually you
can actually benefit from as well the
idea of like maybe there's some ordering
to that to-do list maybe we've talked
about like batching things together and
things like that so maybe it makes sense
to do these three tasks and then these
other three tasks because they are very
familiar or it may make sense to do this
task and do this very different task
because it allows you to switch gears it
forces you to take a little bit of a
break so think about your why on your
to-do list and that's what I want you to
do is for the next week there as a
challenge is every day when you build
your to-do list before you dive into it
take just a couple of minutes and think
about each of those items maybe you add
another level detail to your list or
some notes or something like that to
remind you what is it that I really need
to accomplish to get this done and then
at any time during the day if you're
sitting there and you're just like I'm
heads down and I'm cranking through
stuff maybe periodically or put a
reminder alert or something like to say
am I actually doing the things I need to
do and this I think will help you with
some of the other things we've talked
about like meetings and if you're
walking around the office and people
start talking to you and you just get
sucked into you know water cooler talk
or whatever because you can say wait a
minute I got to get back and do this
thing I think it's going to help you
stay focused it's going to help you
first personally to avoid rabbit Trails
but then also when you're dealing with
other people and I want to throw that to
you Michael give you sort of the last
word on
this yeah so it's I kind of like where
you went with that so the other thing
with that is you know
don't be busy be productive you know
don't be the person running around the
office with your cell phone on making it
look like you're busy you're talking to
someone be at your desk be present get
your work done stay
focused and you're going to see probably
an improvement in productivity and a
decrease in uh
distractions so one of the things that's
very productive that you can do right
now is write us an email send us an
email at info@ develop ur.com
you can also contact us out on Facebook
at the developer Nur site you can check
us out on developer.com there's contact
forms there you can provide comment
comments and feedback on any of our
content that's out there which is
literally over thousands of Articles out
there between podcasts and videos and
blog articles and all kinds of stuff
wide range of technologies that we cover
uh everything for beginning developers
and there's even some more advanced
Topics in there as well love for you to
check that out you can also find a lot
of the video stuff
amazingly enough out on YouTube we've
got lots of stuff there on the
development or channel uh old Mentor
sessions and presentations of varing
sorts and then a lot of these you may
even be there hello to all of you that
in the YouTube audience uh because we
also do the podcast uh we have a video
version of that as well every uh
actually every couple of days when we
put these things out feel free to also
leave us feedback on wherever you listen
to podcast because there's so many of
those out there the Pod catchers that
are out there uh would love to get
feedback from you whe good or bad we
just want feedback because we want to
know how we can serve you better We Want
To Build The Better developers but we're
also building a better podcast in doing
so at least that's our goal that's our
why so now I'm going to let you to
continue your productive day go out
there and have yourself a great day a
great week and we will talk to you next
time bonus
material so I was thinking through this
one um
it kind of bleeds into some of the other
podcasts as far as the bonus stuff but
again as you're going through your daily
processes as you're trying to figure out
your why you know write those lists make
sure you keep track of what it is you're
supposed to be doing uh so that you can
kind of check off and go okay yes I was
trying I need to get this done I need to
get this done but also as you're looking
at those lists and you're making those
checks make sure that you're Focus focus
is on what it is and that you're staying
within the scope of your task so you
don't essentially have scope creep like
we talked about where you get stuck on a
low button adding all that functionality
and feature stick
to the scope of what your task is meant
to be if your scope if your task is too
broad yes you're going to run into that
issue where your focus is going to be
jumping all over the place look at your
task break it down redefine it and make
that that scope I me I think in testing
terms if then there should be a oneway
path to get to the end of your task now
how you get to that path maybe chopping
down trees maybe getting on the
interstate but how you get there is the
journey but you have to
Define your starting point and then
Define your destination and then your
focus and your scope is going to be to
get from A to B you shouldn't have a to
B to C to D to D back to B it should be
straight A to
B that's I like the the path analogy
because I'm thinking about that just as
something that that may help you guys
out there and gals is think about making
if you're going through you know a
heavily forested area or something like
that and you're trying to hack your way
and make a path well the goal is to have
a path through there the goal is not to
have necessarily a pretty path so if
you're if you're whacking away at the
big things and clearing out a a way
through so people can walk through it
then you are being productive if you're
going through and you're like trimming
the sides of the flower so it's far
enough out and you know there's not like
one branch out of place or something
like that then you're probably not
serving the greater purpose and while
that may be useful to some extent and
you can argue that like well somebody
could get hurt that little Branch could
whack them and they could draw blood and
they could die from bleeding to death or
something like we can we can find ways
to argue the importance of our stuff but
honestly if we're arguing that there's
importance to it even with ourselves and
it's probably not that important and
it's like it's really that argument
should be should I do it at all then you
can have that longer argument of yes
it's at least worth it to some point
come back to it but if you're arguing
right now whether there's important
enough to do it today then you probably
should just pass on that the bonus thing
I want to talk about is
really timeliness of getting stuff done
because that's we we touched on it a
little bit through the episode but I
really want to go back to that cuz when
you think of what is now sort of a has
become a big thing like the just in time
delivery just in time
fulfillment and it's really that's what
scrum and agile is about when we talk
about development is it's about doing it
when it needs to be done and not doing
it sooner and not doing it later and so
this is where especially we talk about
like maybe visual design and
functionality and things like that and
this is where particularly we're I think
it helps us when we're designing
software this a little bit one of those
Advanced Techniques or whatever is that
you you can look at the big picture like
what am I what's the problem I'm solving
what are the the steps to solve that
problem and then looking at those steps
is there commonality Michael mentioned
the idea of like components and things
like that so maybe you've got a solution
that's got a bunch of dropdowns and
maybe it makes sense to just each time
you do that build your drop down and do
your little list but maybe in looking at
it it is worth it it is a worthwhile
investment to instead say I have to do
this 10 different times and instead of
doing it in a larger sense and you know
having a lot of work 10 different times
I can do it once and then plug a couple
of things in so it's a talks about the
idea we're think about like code reuse
and things like that so looking at the
big picture and then find the way and
this is sort of to prioritize is first
there's the things that we're going to
use a lot which goes to sometimes why
there's struggle early on and you know
we're building a product because we're
really building a framework of some sort
it may not be a full-blown framework but
it's essentially the framework for this
solution for this product for this
application and so we're building these
pieces and it's things like you know it
is it's the general looking feel and
some things like that that we're going
to spend a little bit of time we're
going to put that there so now we have
placeholders for the features that we're
going to build later and so we need to
think about am I building something
right now that I'm going to actually
replace with a general solution later or
am I building something this is when
it's done it's going to be done and
that's sort of the follow-up to that is
is understanding and it goes back to the
challenge of the week is it's
understanding what does done mean what
does complete mean for this list item
for this thing that's on my task and if
I do that I think that will help me I
know it helps me and I'm hoping it will
help you I in the global sense hopefully
when you're doing that it will help you
maintain that focus and so like Michael
said it's one of those when you say I'm
going to work on this task you know that
this is where I'm at and because you
know what the goal of that task what is
completion for that task then you can
make sure you're focused on getting to
completion and anything that takes you
off of that path you can rain yourself
back in and get to the completion of
your
task that being said we have gone a
little bit I guess not too long but
little over on this one mostly because
we were trying to figure out what the
heck we're going to talk about and I
think it did turn out pretty good so
stick around because we'll probably do
this again in the very near future that
being said go out there and help
yourself a great day I'm going to go
have some more tea because I'm not
caffeinated enough and we will talk to
you next time
[Music]