The texture of your code
I’ve been thinking about intuitive methods of code review. Last week, I read an article about the Japanese onomatopoeic words used to describe texture that resonated with something I’ve been inkling about for a bit.
I’ve been thinking about intuitive methods of code review. Last week, I read an article about the Japanese onomatopoeic words used to describe texture that resonated with something I’ve been inkling about for a bit.
I have known Krishna since interviewing him over a scrambled, laggy Skype connection for a position with me at Aggrego. That was in December of 2013. We decided to hire him, and I am lucky we did.
When I moved my site to yet another format, I had a chance to remove client-side analytics. I had been thinking about removing it for a couple months.
Whenever I come across an interesting article or piece of writing, I add it to my reading list.
I’ve been writing two main types of Go programs recently. One routes http input through a series of transformations and calculations and one receives http input to transform or return data stores.
A new release of gatrack is out today.
In the official Google Analytics iOS SDK documentation, this function call will enable Display Features in your app:
From The Verge, This is Uber’s playbook for sabotaging Lyft:
I’m releasing a new gatrack.js this week (previously introduced back in January). Amongst some minor fallback improvements, the main changes are:
I was eager to back the Kickstarter campaign for the first physical issue of The Great Discontent back in early February. The investment paid off on Thursday afternoon when I picked up my copy from the mailroom.
Update: This API has since been retired.