RGB Values that exceed 255 and beyond (tested up to 10,000,000) give weird behaviors, some transparency effect with the black background give a gradient kind of effect (http://lab46.g7n.org/~dschmitt/cos0.php).

We are now getting into reading, writing, and appending to files for our sam0 project. Learned some tricks with ascii characters, like +32 for uppercase gives lowercase, and vice versa. After a deep conversations regarding various legal / ethical problems, we discovered dinosaurs with hats ( UP UP DOWN DOWN LEFT RIGHT LEFT RIGHT B AAAAAAAAA ).

Haven't figured out how to do gif's fully with GD yet, want to make my spiral spin, would be dope.

Just fully grasping the concept of file pointers. Taking Unix simultaneously provides good practice with raw data, files, and memory in general.

Everything seems great so far. Glad we're doing different logic/math based concepts overall.

Still looking to do a snake game when I get a chance.

We're now getting into C++ a little more than specifically C. This will be interesting and I cannot wait to see what we'll be doing. I have a previous background in Java programming, and it seems that many of the same concepts can be applied to C++. As Matt described, Object oriented programming is nothing more than structure to pre-existing programming.

The above three all have a lot of similarities in my head, as I dealt with them often in Java and make it harder to distinguish. Other than that, I'm pretty excited to dive into C++ a little more.

Not much so far. In unix and c/cpp we have been doing a lot more byte manipulation, and while it is fun, it can take some time to wrap your head around certain things. Still having fun, so that's what's important.

We've been going over some useful commands / tricks for the Unix operating system. We learned how to assign variables and use those variables in practical scenarios, such as with the full quotes (''), half quotes (““), and back quotes (``). We've also been going over how to puff-puff-pass some output to another program using the pipe (|) command. We've also been exploring the permissions of files using ls -l and the chmod command to change those permissions. I've also completed the first puzzle box project for the class, which was fairly easy. The main concept was that each file was renamed to have a different “extension” as to make it not easy to know that some files were tar archives, for example. The commands used were tar -xvf <file> to extract the hidden tar archive, uudecode <file> to decode a uuencodeed file, and again uudecode to decode the BASE64 encoded file.

This is significant because we're just learning the basics of this operating system in some fun puzzle kind of ways. We're learning the significance of many of these commands as well as how we can manipulate the output and input for these commands.

Everything seems to be pretty simple so far.

Just finished up the major UDR 2 project, which included a lot of BASH scripting. This project included a LOT of binary searching. Every packet begin with 41 34 .., and we had to filter certain things to achieve certain things. It was great.

The trick is that we can only do the assignment every 2 hours, which is slightly annoying. This hinders on my ability to pump out the assignment immediately.

This is significant because permissions are very helpful when dealing with files that need to be public, private, or group local.

Everything is coming together nicely, still getting used to REGEX patterns, specifically grouping mechanics. \(\)

SED Usage: s/PATTERN/REPLACEMENT/