Like a lot of programmers, I've begun to wonder what all the fuss is about regarding HTML5. Casting about, I found Mark Pilgrim's fantastic tutorial on HTML5, appropriately titled "Dive into HTML5". I've been mucking with the canvas element, testing out the basics, and I put together a small web page showing a very simple random but colorful "box" generator.
I finished my version of Tetris, and it's now available for you to try on your PC. I set a goal of finishing the game before Super Bowl XLV, and there turned out to be a lot to.
My implementation of Tetris is nearly finished! It plays pretty decently, which is the measure of any game. There's no sound right now, but there's a help screen and a modest splash screen. My goal is to release it before the Super Bowl XLV (February 6, 2011).
While teaching myself Microsoft DirectX, I fell into an issue that is best described as "invisible geometry". This is the unfortunate situation when lines aren't appearing when and where you expect them to. You've told DirectX to draw something, but you don't see it. The difficulties with getting this simple "two-faced triangle" to draw seemed to represent the difficulties with working with DirectX in general.
I added a tag cloud to this BLOG. It looks quite nice, and I was happy with the tags except when I saw that that they didn't accurately reflect my content.
When I first deployed this change, the biggest tag was for "drupal", but when you clicked on that tag, you saw only one story. And conversely, the "c++" tag is smaller than the "drupal" tag, but there are three "c++" stories. Why was the "drupal" tag so large? And why was the "c++" tag so small?
In the world of Java development, you're bound to throw some projects into Eclipse that fill up the Problems View with so many issues that this view becomes unusable. That happened to me, and it quickly reduced my productivity. This view lets you find compilation and build issues that require fixing. The team leader on my project said "you've got a lot of errors there; let's filter them." He showed me how, and I was amazed. Apparently, this great and obvious piece of functionality was available, seemingly right under my nose!
I spend a lot of time in the DOS Command Window. And I spend a lot of time being curious about my Windows PATH. Examining the directories in your PATH can be a demoralizing exercise, but a Perl one-liner makes reading it very manageable.
My electronic notebook saved me today. I had a technical problem here at work, involving some old internal software. I vaguely remember using this software, but instead of rummaging through old e-mails or polling my co-workers I grepped my electronic notebook. I was able to find notes from the first time I used this software nearly two years ago. Rereading these put enough details into my head to be back "up to speed." I felt pretty smug. Electronic notebooks are my personal "best practice."