Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-portfolio domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/lizetta/blog.lizetta.com/wp-includes/functions.php on line 6114
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
Warning: Cannot modify header information - headers already sent by (output started at /home/lizetta/blog.lizetta.com/wp-includes/functions.php:6114) in /home/lizetta/blog.lizetta.com/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":4616,"date":"2024-03-12T23:15:31","date_gmt":"2024-03-12T23:15:31","guid":{"rendered":"https:\/\/blog.lizetta.com\/?p=4616"},"modified":"2024-03-12T23:23:54","modified_gmt":"2024-03-12T23:23:54","slug":"i-would-walk-one-thousand-miles","status":"publish","type":"post","link":"https:\/\/blog.lizetta.com\/2024\/03\/12\/i-would-walk-one-thousand-miles\/","title":{"rendered":"I would walk one thousand miles\u2026"},"content":{"rendered":"\n
Since 2017, I\u2019ve set myself the challenge of walking one thousand miles per year. Not for any particular reason, I just wanted to walk more and I think I saw someone referring to that distance as a good goal for a year so I went with it.<\/p>\n\n\n\n
The first couple of years I easily hit my goal, helped by the fact I met Adam who walks 5 miles a day just by walking too and from work. I tracked my mileage using the health app on my phone and set up a nice little spreadsheet with graphs to show my progress. It was interesting seeing the peaks – often coinciding with a holiday somewhere – and the troughs. Then lockdown hit, and whilst I still hit my goal in 2020 thanks to all the lockdown walks when we couldn\u2019t do much else, the shift in lifestyle definitely had an impact on my movement.<\/p>\n\n\n\n
In 2021 and 2022 I hit over 900 miles, but I was a long way from my target. I thought I\u2019d got back in my stride last year, but I missed the target by just 18 miles. A move back to full time working from home in November was partly to blame.<\/p>\n\n\n\n