[originally posted 2013-08-11]
Thanks for stopping by.
I used to maintain this blog on github using Hexo, a Node.js module supporting markdown. I’ve switched over to wordpress online once I found it supported markdown (in the Settings section) so I wouldn’t have to go through all the rebuilding and deploying for such simple things as fixing a typo.
Who Am I
I Like Test-Driven Development
I really like test-driven development. TDD helps me keep things simpler, flatter, readable, and explainable. If I don’t understand where the tests are going or how to get there, then it’s time to stop and get help or re-think the problem – mainly to avoid checking something in that will harm others’ understanding and productivity.
The list of TDD advantages below is copied from a comment on Cedric Beust’s blog:
- Less fragility
- Less time wasted
Things I Don’t Like
As a front-end developer, there are just some things about development I don’t like:
- tag soup
- the culture of hacking and rushing (to borrow a tweet from Alan Cooper))
AMD doesn’t count on Node.JS)
- CSS’s lack of variables
- CSS’s lack of modules
- reliance on pre-processors to solve these issues
- the in-fill rushing of experts solving these lacunae
- expert opinions on performance
- opinions in general
On the Fence
I’m Not Sure About Pre-processors:
- JS pre-processors (CoffeeScript) (although CS does some interesting things)
- HTML pre-processors (jade, haml, markdown) (although hexo uses markdown)
- CSS pre-processors (Sass, LESS, Stylus) (although hexo uses stylus)
- ANY pre-processors and source transformation steps (browserify, uglify,
Code should work with as little modification as possible.
Disclaimer, of course
Being opinionated myself, and occasionally correct, I reserve the right to change my mind on these topics.