The TinyMUX project depends on Google Code for issue management and for the top, public-facing half of its source code control (subversion). For some time, Google Code has supported diffs from within the browser, and recently Google has added the ability to request and conduct code reviews of changes.
However, there is a limit. Code reviews [...]
Archive for July, 2008
Google Code Limits
Posted in Technical on July 26, 2008 | Leave a Comment »
Yellowstone Forces
Posted in Senses, tagged Yellowstone on July 25, 2008 | 1 Comment »
Yellowstone is full of sights, colors, smells, and danger.
The sulfuric springs and geysers are acidic and have a rotten-egg smell. In fact, our kids found normal, non-rotten eggs unappetizing at times because of the associated smell. Some springs are acidic enough to turn clothing to ashes and dissolve flesh.
Some of the acidic springs dissolve the [...]
Insight from CRC to RS
Posted in Technical, tagged software on July 25, 2008 | Leave a Comment »
You may be familiar with Cyclic-Redundancy Check (CRC) codes and how they are capable of detecting burst-errors up to the length of the code (e.g., an 32-bit CRC can detect any 4 consecutive bytes of error). There are other forms of errors that these codes can detect as well.
You may even have heard that for [...]
Purpose
Posted in Technical on July 25, 2008 | Leave a Comment »
The plan for this blog is to describe real code in real environments from a get-it-done engineering perspective. The TinyMUX project will appear frequently but not exclusively.
The ‘D’ word
Posted in Uncategorized on July 22, 2008 | Leave a Comment »
After two weeks of Yellowstone, and a few days to give the sunburn a chance to heal, I’ve decided to get back on the diet bandwagon. I’m using the same model (with the same softcode) I did last time.
Weigh and take three measurements with a tailor’s tape measure.
Use Navy method to determine goal and Basal [...]