Posts

Showing posts from December, 2017

Reflection on Blown to Bits Pages 32-36

I found this Blown to Bits reading interesting. It's shocking to me that it was so easy for the computer science professor to identify everyone in the "de-uniqued" medical data, using just voting information. This really shows how important it is to completely "de-unique" your data, or just not release it to the public at all! What information can you find about people here?  Provide at least 4 examples of how this information could be used in a manner that could compromise someone's privacy and have a negative impact on their lives. Like in Blown to Bits, just using basic outside information such as the census bureau or voting statistics, you can gather lots of information about people and connect it to the medical data. Using this information, you could sell their information to advertisers, sell it back to them, use it against them, or use it to threaten them.

Digital Scene Reflection

Provide an overview of the purpose of your program and how your program code works. Describe the most important program features, rather than providing a line-by-line summary of the program code. -The program designs the individual pieces of a grassy field. It first designs the Sun, ground, and grass, then draws flowers, and finally completes the scene with sheep and fluffy clouds., Describe the most difficult programming problem you encountered while writing your individual code. What was the difficulty? Explain how you resolved it. The most difficult part of programming my code was figuring out how to draw the edge lines that made up the border of the sun. Since the sun was a large dot, I had to find a way to write a program that drew each individual line of the sun. In order to do this, I ended up using moveForward, turnLeft, and moveBackward.  With these commands, I was able to complete my sun. Identify an abstraction used in your program and explain how it helped ma...

Digital Scene Project

penColor("rgb(0,0,255)"); dot(300); sun(); ground(); grass(15); function sun() {   //start   penUp();   moveTo(50, 50);   penDown();   //draw main dot of sun   penColor("rgb(255,255,0)");   dot(35);   //draw edge lines of sun   //note: code cannot be looped as every edge is different.   moveTo(70, 80);   turnRight(140);   penWidth(5);   moveForward(17);   turnRight(180);   moveForward(17);   turnRight(70);   moveForward(20);   turnRight(90);   moveForward(20);   turnRight(180);   moveForward(20);   turnRight(65);   moveForward(20);   turnRight(90);   moveForward(21);   turnRight(180);   moveForward(22);   turnRight(50);   moveForward(17);   turnRight(90);   moveForward(24);   turnRight(180);   moveForward(20);   turnRight(50);   moveForward(13);   turnRight(80);  ...

Reflection on Text Compression

1: Do you think it's possible to describe (or write) a specific set of instructions that a person could follow that would always result in better text compression than your heuristic? Why or why not? - I think it would be possible since the heuristics are not very accurate and are sometimes confusing. A specific set of instructions written by a person would result in a clearer protocol which would lead to faster and clearer text compression.

Unit 3, Lesson 6, Puzzle 2 Code

function turnAround() {   turnLeft();   turnLeft(); } function right() {   turnLeft();   turnLeft();   turnLeft(); } function tDrawingUP() {   moveForward();   moveForward();   moveForward();   turnAround();   moveForward();   turnLeft();   moveForward();   turnAround();   moveForward();   moveForward();   turnAround();   moveForward();   right();   moveForward();   moveForward();   turnAround(); } tDrawingUP(); function tDrawingRIGHT() {   right();   moveForward();   moveForward();   moveForward();   turnAround();   moveForward();   turnLeft();   moveForward();   turnAround();   moveForward();   moveForward();   turnAround();   moveForward();   right();   moveForward();   moveForward();   turnAround(); } tDrawingRIGHT(); function tDrawingDOWN() { ...

Programming with Simple Commands Reflection

What surprised you about programming with such a small set of basic commands? Were you able to be creative with such a limited set of tools? What was most frustrating about this activity? If you could add one additional simple command, what would it be, and why? -I was surprised by the small set of basic commands; however I was able to find success in making the turtle move around. I got creative, using three "turn left" commands to make the turtle turn right, and using "turn left" to turn left. This was a challenge at first, but I was able to solve my problems by being creative. The most frustrating part of this activity was trying to program a “turn right” command. Through trial and error, however, I was able to accomplish this.

Turtle Coding: Efficiency in Programming

Define efficiency in programming: Term used to depict the reliability, speed and programming methodology used in developing codes for an application. Code efficiency is directly linked with algorithmic efficiency and the speed of runtime execution for software. When we are trying to be "efficient" in our programming what are some (valuable) resources we might be concerned with?  Why does it matter? -When we are trying to be “efficient” in our programming, we have to be concerned with the amount of commands we are using. Always being aware of where we are potentially using too many commands is a big part of programming. What strategies or reasoning did you use to identify possible solutions? -First, I followed the program instructions to make the turtle move the way it was supposed to. After that, I looked at the code and found ways to cut down on the amount of lines of code I had. Is the solution that you or another group found the most efficient? How do you know?...