Deprecated: Assigning the return value of new by reference is deprecated in /homepages/30/d177037045/htdocs/1h29/blog/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/30/d177037045/htdocs/1h29/blog/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/30/d177037045/htdocs/1h29/blog/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/30/d177037045/htdocs/1h29/blog/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/30/d177037045/htdocs/1h29/blog/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/plugin.php on line 339
 Carnet d’entraînement au Semi Marathon Lyon - Mes objectifs 1h39 puis 1h29 » Blog Archive » Enfin une semaine avec des séances de footing
Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/plugin.php on line 339

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/functions.php on line 55

Enfin une semaine avec des séances de footing

Rédigé par Eric | Catégorie : Dans la tête


Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/plugin.php on line 166

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 514

Grand silence sur ce blog, pour grande période de convalescence ! La reprise du footing a pris beaucoup, beaucoup plus de temps que prévu. C’est seulement depuis 1 mois, début janvier que j’enchaine des petites séances de footing (35 min) sans avoir le genou qui gonfle trop !

Pour faire court et surtout passer à la suite, voici comme c’est passée ma réduc depuis l’opération. Je précise que mon job de chef d’entreprise, que mon hygiène de vie et que ma motivation ne sont pas exemplaires pour reprendre dans les meilleurs conditions. Je reste tout de même septique sur la possibilité de reprendre le footing 45 jours après l’opération, à moins d’avoir à sa disposition une équipe médicale d’un sportif de haut niveau ! Pour ma part, début octobre, je ne pouvais pas courir : genou qui gonflait vite et petites douleurs à l’effort, bonne fonte des muscles de la cuisse et manque de souplesse. Depuis j’ai fais de nombreuses séances de kiné pour reprendre du muscle, des ligaments en bonne état et une bonne souplesse de tout cela. Mes séances étaient constituées de 30 min de travail avec le kiné et 30 min de vélo elliptique. Pas très fan de sport en salle, j’ai pris gout à cet engin.

A ce jour, le genou est en assez cette bonne condition, j’ai pu skier plusieurs fois, je fais 2 petites séances de footing par semaine : 35 min et une séance de kiné avec vélo elliptique. Le genou semble gonfler de moins en moins…

Donc les jours qui arrivent devraient me permettre de reprendre petit à petit de vrais séances de footing et aller progressivement vers 3 séances hebdomadaires et enclencher un plan d’entrainement pour un semi en 1h39 !

Volontairement, je n’ai pas et je ne vais donner de détails médicaux sur mon genou, je ne pense pas que le net soit l’idéal pour cela. Je ne voudrais surtout pas que des lecteurs se “servent” de mes écrits pour décider ou non d’une éventuelle arthroscopie du genou ! Donc là je reprend la course à pied et mon récit sera surtout celui d’une reprise et un bon fil conducteur pour garder la motivation et échanger avec vous !

Rédigé par Eric


Commentaires (2)


  1. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/plugin.php on line 166

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 522

    Bravo pour ton courage et ta motivation!


  2. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-includes/plugin.php on line 166

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/30/d177037045/htdocs/1h29/blog/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 522

    Dommage que tu ne donnes pas plus de détails sur ton opération. Les internautes ayant ce genre de problème aurait pu trouver tes infos utiles.

Ecrire un commentaire

Carnet d’entraînement au Semi Marathon Lyon - Mes objectifs 1h39 puis 1h29 Rss