The plan was to have fun with Google’s speech API, but that didn’t happen. No. Totes not true. I had a great time with it over in Codepen.io; however, my own local host and Chrome duked it out in the “Who can be the biggest jackhole” contest. I tried settings on my laptop. I tried Chrome settings. I Googled. I searched Slack Overlord. I asked real humans in touching distance. Nuffink. I won’t go into it other than to say that there may have been emails, slacks messages, and tweets that were in all caps. RAGE AGAINST THIS MACHINE OR SERVER!

Why this sucked glass shards was that I couldn’t test the JavaScript functionality of it. Not without adding, committing, pushing, testing, rinsing, lathering, and repeating. What a waste of time. I have three hounds at home. Two of them decided to eat that (don’t know what that is) and my weekend was spent checking the Googles for answers between cleaning up squirts and steam cleaning carpets. I’m not a prissy woman, but even I get over cleaning up Satan’s pudding multiple times a day.

Not one hour of uninterrupted code.

So this is where I settled for now: Whisper sweet nothings to Divvie.

How happy am I with it? If I were to lighten up my inner Francis, I’d say very. It was a lot of fun and there’s so much potential. My frustration with the mic was a huge stumbling block. I’ll still work on why, but if I put this project to bed, at least I won’t have that poo-flinging monkey on my back. I would return to Divvie and DRY it out. Use object-oriented programming. OR address the need to do this again but DRYer and try something new.  I KNOW I KNOW I KNOW!! I have wanted to do a German “der die das” game. That would work for OOP. OOP there it is!

Silver lining? I realize how much I love to code and learn how to better code when I do this for fun even when I’m exhausted from being the hounds’ poo bitch.

That’s win.