technical writing
6 = ^
August 2, 2012 - 4:26pm — mslaybauA lesson I learned today:
If you have some code that just isn't right, or writing about programming and the math doesn't work out, look for a number that ends in ...616, ...632, or ...664. It's likely that someone was writing x^16, x^32, or x^64 and didn't hit shift hard enough to make the carat appear.
In my case, the number was 2632, which really should have been 2^32, or 4294967296 - 6 orders of magnitude different.
