Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp 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 /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the worth-the-read 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 /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home2/sisikunm/public_html/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home2/sisikunm/public_html/wp-includes/functions.php:6131) in /home2/sisikunm/public_html/wp-includes/feed-rss2-comments.php on line 8
Comments on: I quit my job and went on a vacation https://www.sisikunmi.com/lifestyle/i-quit-my-job-and-went-on-a-vacation/?utm_source=rss&utm_medium=rss&utm_campaign=i-quit-my-job-and-went-on-a-vacation Live. Learn. Inspire Wed, 28 Dec 2022 15:41:52 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Olakunmi Ogunyemi https://www.sisikunmi.com/lifestyle/i-quit-my-job-and-went-on-a-vacation/#comment-4184 Wed, 28 Dec 2022 15:41:52 +0000 https://www.sisikunmi.com/?p=2808#comment-4184 In reply to Bukky.

Hi Bukky, thank you! I did get a very fantastic offer and doing greatly so far.

]]> By: Bukky https://www.sisikunmi.com/lifestyle/i-quit-my-job-and-went-on-a-vacation/#comment-4180 Wed, 28 Dec 2022 14:05:02 +0000 https://www.sisikunmi.com/?p=2808#comment-4180 You’re brave for quitting your job and searching for something better.

I’ve been in your situation a few times, also because I felt it was time to move on. Each job I’ve resigned from, has led me into a position better than the previous one(s).

I’m sure you’ll secure (or have secured) something better.

xoxo

]]>