Less than 12 hours until my Monday weigh-in, so I figured I had better check in with an update on my week since Thursday.
When I posted then, I was only down about 0.2 lbs for the week, thanks to an unexpected Monday night binge. I told myself that it would be nice to try and aim for a solid pound loss by the end of the week, which would mean losing 0.8 lbs in the last three days - not impossible in theory, but unlikely given my recent rate of loss.
However, I stuck to my diet and exercise, and by Saturday morning I was really close to that pound. The thing is, I was due to start a 15-hour all-night on-call shift at my new hospital on Saturday night. In anticipation of that, I went against my own rules, and actually loaded up on a few carbs, to make sure I had the energy to get through it.
Well, never have I been so disappointed to be given the night off, as our consultant was heading home, and the junior doctors didn't know what to do with us students once all the patients were asleep, so we were sent home too! I'd done the loading for nothing! (well, still a few hours on our feet, but still!)
To try and make sure we got enough hours in, my colleague and I decided to go back in first thing this morning for the ward round. As such, I just snatched some sleep last night and forgot to weigh this morning...that means I have no idea what impact, if any, my carb load on Saturday morning has had on my weight. It could be I have put on some water weight, and might have quite a small loss. It could be that being back at Uni and on my feet all day, plus the fact that I've run four times this week, has burned off any weight the carbs might add. I just don't know. I have no idea what to expect tomorrow morning!
Talking of the running, as I say I managed 4 runs this week, which is just over 17 miles, so I'm pleased with that. The funny thing is, each night I've been convinced I was running faster than the last time, but I have in fact been getting slower! It always used to be the other way around (if I thought I was slow, I'd actually been quick), but I'd never noticed it working this way round before - very strange!