Two ways to kill code mojo

Break my motorcycle. Break my quadriceps.

Thursday: I read about coding, specifically Ember. I had plans to hit the EmberATX meet-up with some pre-knowledge. I knew that I’d be a kindergartener listening to Ph.D.s, but there’d be things I’d pick up. No one quizzed me. This was not mojo killing. It was mojo filling.

It’s walking out to your motorcycle and seeing that someone knocked it over, buggered up the paint, broke mirrors and lights. To really kill my mojo, they left a note with a false number. I did not ride home from the meet-up, and run inside to read more about Ember and fiddle with my Color Palette. Nerp. I rode home cautiously without functioning mirror. I covered up P.J. Soles (my bike), and went inside to look at mirrors online and think about the $$$ whooshing out my accounts.

Tomorrow. Yes! After a bad day, I’ll enjoy a Friday in and code.

Then this happened when tomorrow became today:

wrongway

I accepted a short-term assignment and proceeded to cycle to the wrong office (10km), then back UPHILL to the correct office (15km) and back home after work (11km). We all know why motorcycling was not an option.

I’m knackered. There’ll be no coding. Not unless I can have an event listener toss my dead ass into bed. I’m even too tired to eat. At least I’ll wake up knowing that I can have frozen scoops of deliciousness for breakfast.

I am hoping that reading about coding will count. Of course it counts. My blog. My rules.

100 Days of Code: Palette with Ember!

The Emberitas hosted a day-long workshop to teach EmberJS. I opted to go with beginners for two very important reasons: better access to the food, didn’t require going outside. I had already walked 30 minutes to get to The Iron Yard. I wasn’t going to walk another meter. And the food was insane. Sure, they took some to the other building, but not as much. Please. Two arms vs a long table? No brainer. I stays. 

I’m not being totally truthful. I wanted to start the app from scratch, and I think I got more out of it doing it that way. Building a static page and then refactoring it was great for the way I learn. Making first the familiar <a> tags and then changing them later to the new-to-me {{link-to}} helpers made sense. It felt like translation. More ah-ha moments. 

It was a great way to spend a Saturday. The Emberitas were playful and knowledgable; the men who came to help as we raised our hands were supportive. Oh, and the swag was insane. The sponsors outdid themselves with the swag, and then made Ember meaningful by sharing how they used it. I was a might sad when it was over.

It wasn’t really over. We didn’t finish. 

And then life got in the way when I had a part-time job to teach coding at a summer camp in Canada. Or Round Rock. Tomayto. Tomahto. I came home each day exhausted. I thought about my own code. I thought about the Ember app. And then I slept. New schedule. Teaching again. Riding home in the baking sun at 1p. Yes. I slept. 

Returning to Ember felt like catching up friends after summer vacation. Emberrrrr! Love you hair! How was camp? Did you make out at the lake with that Robbins kid with the cool haircut? The Emberitas did such a fantastic job with their notes, codes, and screenshots that I had no problem picking up after that time off and finishing my app:

Palette-o-Rama!

Yay! I have a palette app. Oh, but I have no palettes. That’s ok. There’s potential. And it’s mine all mine! 

So. What next?