Decide what not to do
Welcome back, internet friend!
Howdy internet friend and welcome back to my blog! Thank you for taking the time to read my weekly update post. I thought I was going to keep this short and sweet, but it turns out I’m not great at that! Last week, I shared my to-do list of all the things I wanted to accomplish, and the week before it was so long I only worked on half the stuff on it. That brings me to the quote of the week, which was shared with me by one of the folx I am mentoring. We were having a chat last Thursday and he mentioned that, “sometimes deciding what not to do can be important.” In the context of giving myself too much to do and then being displeased at not accomplishing all of it, this hit really close to home. So in this weeks blog post, I wanted to share how that insight will impact my future plans, as well as discussing what I accomplished last week. First, since this is a wrap-up post, I’ll start with what I accomplished last week. Also, I’m going to add a new section at the end of this post for weekly greetz. I’ll include the Twitter handles of a few people who helped me this week. Without any further adieu, let’s look at what I hoped to accomplish last week.
If you read the last post here you might remember that I had a list of about seven things that I wanted to accomplish. Like last week, I was only able to do about two or three things on that list. So, taking the advice of my mentee, this week I’m only going to set three goals for myself.
- Spend time every work day going through the Udemy course on Go I purchased.
- If there is a morning I’m not feeling motivated to code, I will spend that morning updating my architecture document for the MUD I’m building.
- Invest some time in trying to resolve the CSS issues for this blog on mobile.
That’s it! I think that I will make my life much easier and reduce the likelihood I end up mad at myself if I just cut down the number of things I want to accomplish each week. Under the best circumstances, I have three hours each morning to work on my own personal projects before starting work. If I use that time efficently I should be able to complete my Go course by next week, and then do a thorough write-up of it here as a special post. After that, I will complete my design document and start coding my MUD.
I think that each week I’m going to limit the things on my to-do list to three or less. That way I’ll increase the likelihood of actually accomplishing all my goals. We’ll check back next week and see if I can hold true to the “3 or less” rule! Will this actually work out? Only time will tell! However, I believe that by setting myself up for success rather than failure, I’m going to have a better time each week. Particularly when it comes to looking over all the previous weeks accomplishments on Monday morning.
Weekly Greetz
This week I want to give a shout out to the following folx:
@cetolyne - great friend, awesome programmer, super helpful!
@blenster - cool maker, very positive, well worth a follow!
@GWeessies - very smart person doing interesting research!
Marley - first place champ! Marley is one of the best on Twitter!
MildThrone - another new bug hunter to keep your eyes on!
Null Coder - another awesome person to keep an eye on!
Those are my recommendations for folx to follow for the week. Come back next week for more suggestions and have an excellent week!
Click here for the previous post and click here for the next post