Ended up playing some video games and then took a two-hour nap. Now it's Friday.
Beauty and the Beast comes out today. Will probably see it after a proper sleep.
Going to play a bit of Overwatch soon here. Been playing as much as four hours a day for a bit, but today it'll probably be less.
Overwatch play has stopped. I will play some more by myself, possibly. But first, food!
Food was quite good (did some kitchen cleaning whilst I made something on the stove).
Watching some Youtubes.
Interrupting youtubes to lay down for a bit.
Got around to lots more youtubes whilst playing FTL on the side.
Let's read some Cracking the Coding Interview.
I'm going to take a route with this book I haven't taken before, but I know may be worth while. I'm going to focus on the sections that seem more relevant to me and skip over everything else. This book is massive, and I may be short on time (I agreed to try for Google soon and would like to make a strong go).
This book seems organized in such a way that it'll be easy to do this. There's even a section early on called "The Google Interview". I won't be reading "The Amazon Interview" or "The Facebook Interview". Not yet, anyways.
Hmmmm.... Being an SDET (software engineer in test) is actually of interest to me. I wonder if profiling is a part of such a job.
The "Before the Inverview" section has some good tips for resume building. As a person with free time, I might want to execute some of these tips if I haven't already.
There's a preparation map!
Hmmmm.... It looks like I got the "1+ Year before interview" part down, thankfully. Personal projects and coding language diversity could be a bit better, but I think it's manageable. I might want to brush up on my C, Java, and bash if I want to keep them on my resume. I might not be able to answer questions about them if asked. Maybe SQL stuff, too.
Sent timeline thoughts to Google friend, and took a "premium sites" break.
Reading a bit of the book made me think of projects I want to work on.
The first thing that comes to mind is something related to FTL. Like, there's a lot I could do. Long-term would be an AI that plays the game, gathers various data, and I reverse engineer it to play on the browser. That's super long term and probably won't happen. Shorter term would be a website helper pretending to be a "computer subsystem". In various sci-fi there's often some AI that gives chances of things happening based on chosen actions. Considering the rather ridiculous amount of events in the game, the RNG nature of the game (which differ based on the area you're exploring), and the various things that allow for new options to events (species represented in crew, installed weapons/drones/systems, etc), there's a lot of chances to consider.
It would also add to the unlock nature of the game. Chances wouldn't automatically be known, the computer would need to be updated with each event and the possible outcomes and their chance of happening would become more complete through repetition.
Maybe I should just start working on it next time I start playing FTL.
Aunt and uncle awake so I hung out with them and made some fries.
Watching some more youtubes now.
Not feeling tired yet. Did have a solid nap in the middle of my "day".
Woke up about 6 hours ago. Lil' cousins were visiting. Watched Trolls and Frozen.
Trolls was the best bad movie I've ever seen (more on that later?).
Played about 5.5 hours of Overwatch. Maybe too much. Maybe need nap. Not sure. Going to probably play FTL.
The lil' cousins are here for whole weekend. Properly distracted by them.