End of Day Review

03/05/15

I stayed at work too long today. Though, work quality was pretty decent, so I suppose it's all good.

I managed to make a plan today! I managed to follow today's plan! Reading on the bus ride home wasn't as good as usual, but that's probably because tired.

I got some good feedback for ideas for my system today. I'll try to implement them. One of those things is to plan the next day during my end-of-day review. Considering my blog post today was about fixing my sleep schedule, and one of my strategies is trying to motivate morning me to wake up, this seems like an especially good idea to try for my home system.

So, I need one hour of non-pomodoro time in the morning to do non-pomodoro work: walk dogs, do misc non-morning routine stuff, etc. Other than that, I would like to devote two pomodoros to non-morning planning/routine stuff. I would also like to leave for work before 9.

Meaning, I want to wake up 3 hours before nine, at least. So, I need to wake up at 6. If I wake up before 6, and can say that I slept at all, I should stay awake to punish sleeping me for waking up before I should have.

Oh, also, morning routine me managed to make my pomodoro log an actual html table. Yeah! I'm already digging the look of it at work and see no reason I won't at home.

Blog wirting went well, but I didn't finish two posts like the other day. It's okay though, the second post required thinking on what to do with my site.

Speaking about my site, and developer productivity in general. I want to start matching my perceived skills with portfolio-level achievements. I think I got enough javascript understanding to say I'm "good" at it, but I got nothing to point at as an example of my abilities. Maybe I'm still really bad at javascript.

Same kinda goes for python, html/css, and even C/C++. Though, my C/C++ isn't "good", I just think I'm functional.

I want to be good at:

• Javascript
• C++
• Profiling
  • Time
  • Memory
  • Flame charts? (There was an article I read a while back called Node.js in Flames
  • Bugs
• Python (to a lesser extent)

Being good means doing good. Doing good starts with doing at all. I'm making progress on a personal productivity system, and even javascript/html/css with my site. I need to make specific projects for things I want to be good at, and specific exercises too, or stop pretending that I'm trying to be good at them in the first place.

This doesn't even take into account hardware stuff I want to learn. I have a lot of work to do, and I need to actually plan for it proper.

Which is why setting aside time to do stuff is so important. Which is why avoiding time sinks like reddit and general web surfing is so important.

I can do it! I believe! I can be good enough to get paid doing freelance stuff! Let's figure that out, too!

Anyways, that's a good enough review for today. Let's do my end of day routine.