There is something small and tiny that I feel I am missing about Test Driven Development. I understand the basic principle of the matter; write a test that fails, then write the code to make it pass, rinse and repeat; red, green, then refactor. Knowing that basic truth of what TDD is has not translated into actually being able to use it as a practice in my day to day coding.

Yikes, I am behind in my reading goal. It is lat in the month of January and I am not far enough along in my reading to hit my goal. I am reading the first book to reach my goal that is my New Year’s resolution to read twelve books this year. It is a small step up from the seven books I read last year. The challenge though is that I am already behind.

Previously I was using a quick fix solution to bust cache on my static css files. Briefly, cache busting is a strategy of uniquely naming CSS and Javascript assets to improve page loads, and speed up propagation of changes when updates to the layout are made. More on cache busting. My previous technique worked as needed but suffered from a couple limitation. I was using random numbers appended to the CSS filename to get a unique filename.

How we name html class names is important. Naming in general is important. A class name is a little story we can tell ourselves. Later in the development process we can quickly and easily know what an element is for based on the name. We learn from a class name what something is, and what we can expect from it. Semantic class naming is a style in which we use class names that describe what an element is, or it’s intended purpose, rather than how it looks.