Previous Entry Share Next Entry
Unit Testing Training
At work, i'm trying to get a lot of work done in a short time and hitting guff because certain decisions haven't been made and various ducks aren't in a row.. frustrating.. but at the same time, i'm helping run a once-a-week class to train my coworkers in various things. This last class was on unit testing.. fun fun.. next week, we're going to take some real code (dealing with Debit card prenoting) and refactor it during the class so that we can add unit tests to it. Should be fun in a very center-stage kind of way, and I *hope* that people can learn from it, because dude, this shit's cool.

If you need to record a screencast, here's what I do:
- CamStudio (opensource). Don't bother with the CamStudio
Screencapture Codec, its a bad route to follow.
- Screen res at 1024x768
- Use Microsoft Mpeg4 version 2 encoder at 1024x768, 500kbps, q=90
- Sysinternal's "ZoomIt" utility
- Frame rate at "automatic" with the slider around 20fps or

The result is: about 1.5 to 2.0 MB per minute (the 500kbps should work out to 3.75 MB/min), almost crystal clear video. A 1.5 hour training class should end up around 500 mb or so, we shall see.  Of course, i only know this after several mistakes, and I haven't tried the solution in the lab just yet.

I like the encoder - it uses time as a component - imagine all the frames stacked up in a 3-D pile, THEN do the fourier transform on it, but do it in a sliding window so that you don't get pre-artifacts, just post-artifacts. The effect of compression is that when a window disappears, you can see a shadow of the window left behind for a bit.. artifacts over time. Cool shit. Especially when you go to really small bitrates. I like Mpeg4, it rocks.


Log in