Day 13, paybuddy and D3.js

I can’t believe it is already two weeks into the class.

Zak, Jake, Sonomi and I took a very nice walk during our two hour lunch break today. It was great to walk around and explore the area with friends. We even went to a cathedral that sits on top of a hill. We joked about we should use D3.js to replicate the cathedral glasses. It would be really cool and when you hover the mouse over, the image would change into Marcus. hehe. That would be nice.

Anyway, there is no formal lecture today.

– Marcus went over the solution for the bind(). It was fairly straightforward but some classmates were still confused.

– Marcus live coded some D3 with us today and it was fun to see him approaching a new library. We struggled around how to get element positions per frame. Then, we realized that d3.transition.tween(‘name’, callback) will run callback() per transition. It also expects callback() to return another function (let’s name it worker(t)), and subsequently it runs worker(t) per frame. It makes total logical sense to separate those two things: actions per transition and actions per frame. But hey, hindsight is always 20 20. In the debug process, the class shouted and offered tons of wrong ideas, myself included. I will try to be more careful next time.

Social life:

– The class went to Karaoke at 6:30pm. Most people went but I didn’t go. Instead, I worked on Paybuddy repo. Paybuddy basically asks you to validate a payment form. It sounds easy, but there were tons of small twists. For example, credit card ccv can be 3 or 4 digits; the month of expiration date needs to be between 1 to 12  and tons of others. It is tedious , but every frontend developer should try it at once. Validation form is hard enough, and all other payment steps are going to be even harder. No wonder Stripe is a big success.

Advertisements
Standard