Personal viewpoint on how the self is shaped.
Experimenting with relative typographic line length limits applied to code.
Removing the tedium from creating, developing, and publishing repos.
Abandonment of an in-browser solution for a website-at-a-glance webpage and looking forward to perceptual diffs.
Mathematical definitions and reasoning behind why abstracted code is maintainable code.
Code coverage is the percentage of lines of code touched by a test suite. It is a good metric but API coverage is a new step forward.
An experiment and attempt at understanding my code patterns.
A presentation overviewing the history of BDD and some of my experiments.
An explanation of my morals/ethics and why I devote my free time to open source.
An introduction to Halo: its good, bad, and ugly parts.
Another overdue introduction -- This time to Builder, a framework for automating common client-side steps.
The following letter is about my thoughts and complaints of the recent gruntjs upgrade from
Warning: This article is more opinionated than other ones.
Below are my most recent pipe dreams for BDD. While the example is based on testing a UI, it is applicable to anything as does BDD.
A screencast on my thoughts on client-side frameworks.
This is a partial continuation of my previous catch up post. I finally got my CSS Off score; 61/100 points and 66th of 417 place.
When UMS' CSS Off started in Late October, I was getting frustrated at needing to manually refresh for any page change -- no matter how small.
A summary of all the contests, scripts I have written, and everything else I meant to write about since my arrival in California.
Sublime Text does not have a proper testing framework. With the disparity of Python 2 and 3, it makes cross-version plugins even harder.
To solve this problem, I am developing a testing framework that can be integrated with Travis CI for full automated tests.
git squash without repetitive conflicts
Bash prompt with colors, git statuses, and git branches