Search the Community

Welcome to my Not Reboot It feels like I need a reboot. A do over. Press stop, wait for everything to come back up, and pick up where I left off. There is an issue with doing that. You never fix the problem I'm an IT guy. My career has advanced and I do some pretty cool shit if I'm honest (I build bits of internet infrastructure). When I was a young man, rather over confident but still only in the education part of my career, a friend of mine came at me with something I'd not come across before. He told me simply. "Your first reaction should never be to turn it off and on again." It might work. It might clear the problem away. It might be necessary to fix it but the first step shouldn't be to reboot. It should be to identify the problem. Or as I like to tell our support staff. "Define 'problem'". If you never find out what the problem is it'll just come back again. So rather and rebooting I'm taking my do over to look at me right now and to figure out what needs to change for me to go forwards. Of course the number of problems you can find at any given time can be seemingly infinite and this isn't an exercise in seeing how many problems can be identified but to solidly define a handful of known issues. So for this challenge I'm going with these: I oversell training resources My eating is currently all over the place Training Resources: Overselling is a term used in my industry to describe the common practice of selling more capacity on a shared system than the system is technically able to sustain. With the idea that not everybody will be using all of the 'guaranteed' resources all the time. This can and does have consequences In training I push more than I am able to sustain and it's not always obvious that I am doing it. Fatigue tends to catch up on you unaware. You can plan for it and you can mitigate it and you can take advantage of some extra few percent of training effect but I genuinely think that this model isn't worth it. So I'm trying to build a sustainable and scalable training model for myself. One that will provide me with the results I'm looking for without the pain So the plan is simple but the execution is going to be a little troublesome. I have a virtual race this Saturday, a 20 mile run that I am hoping to get below 3 hours. So that's going to be a hard run for me. At the very least I'd like to get a 20 mile PR (currently 3:15) since I'm feeling confident I'm in a place where I can actually pull that off. That said I've never actually tried to do what I am going to attempt so all bets are off Once that is over I am going to be resting a little through week 1 so this experiment isn't going to get underway properly until week 2 but there is no reason I cannot start as I mean to go on. I've set my current mileage limit at 30 miles per week. I don't intend on going above that for the duration of the challenge (I'm not going to be 100% strict on that 31 miles isn't going to make the difference) but the goal is to keep it at about 30 miles. I'll be doing a speed workout and a threshold workout each week. The goal is to keep a training log along with a session rpe. I'm going to be using this to keep track of my load. The goal for my load to remain fairly constant for the entire challenge but I expect week 1 to be quite light Eating: Okay as a knock on effect of my long term illness my hunger sense seems to have gone a little crazy. So my goal here is to keep a food log and it's more of an attempt to make sure I'm actually eating enough rather than too much because I've been skipping a lot of meals because I don't know that I"m hungry until I actually start eating. I'll take this over feeling like I was going to throw up every time I ate for 6 months but it's presenting a new problem for me. Simply being mindful of it might be enough to fix it. Well that's it An overall goal for this will be to try and make sure I update every day. Since keeping the logs is kind of the point of the challenge