Digital Design Journal by Jawad Rahman

     G4C is an organization that promotes real-world changes by motivating game developers to create games that expose people to problems in the world. G4C holds annual game competitions for given themes, or issues. For this year's G4C competition I worked with a team, Team Kakushin ( 革新) , to create a game with the theme of 2050 Automated Communities, a theme about how life in the coming decades could be very different, for better or worse, due to advances in technology. The amount of potential technological advances and their various effects by 2050 was huge, so my team decided to hone in on one technology likely to make a massive change in our lives - Artificial Intelligence.      The first thing my team had to figure out before making the actual game was what to make the game with. There was some experimentation done on which platform and programming language to use but eventually we settled on using JavaScript on Code.org's App Lab. Next came deciding what type of game we

     Lab 20 incorporated many of the things we learned from Lab 18, with the functionality holding many similarities. In Lab 20 we were to create a webpage that compares 2 numbers, x and y. The user is supposed to be able to see if x is greater than y, y is greater than x, x and y are equal, etc. The interface is similar to Lab 18; there is an area to input two values, there is an area with many buttons that lead to a specific outcome, and there is an area to view what the outcome is. Unlike Lab 18, the buttons don't perform an arithmetic operation on the 2 values but check if a certain comparison between the 2 values is true or false. The result area, instead of displaying the result of an arithmetic operation done on 2 numbers, displays if a certain comparison between 2 values is true or false, essentially displaying the result of clicking the now comparison buttons.      I started Lab 20 just like I started Lab 19, by duplicating the code for Lab 18. There was not much to chan

     Lab 19 was very similar in functionality to Lab 18. This lab revolved around reassignment operators, or changing a number to be a different value. We needed to give the user an initial value and a place to input a second value of their choosing. The user would also be given buttons they can use to perform arithmetic functions on the initial value with the second value they input. Any change to the initial value would need to be reflected in area that displayed the result of the transformation as well as the area that displayed the initial value. The first thing I did in creating this lab was copying my code from Lab 18. Since 18 had pretty much all that I needed for 19 all I needed to do was copy it and change a few lines of code. One change I made in the HTML was the first value input. In 18 the user could input 2 values, a first and second value, but in 19 the user must input only 1, a second value that will be used in an arithmetic function to change the initial value. I delete

     The AP CSP Create Task requires students apply their skills of programming to create a computer program through an incremental and iterative process. This task gives students the opportunity to collaborate making this program which I took, creating the program with 2 other students. The first step in the process was coming up with an idea for the game. We considered what the story would be, how the game would be played, what was the eventual goal, and many other things. The idea my team eventually came up with was a survival game in which the user dodges falling rocks and tries to survive as long as possible. We then needed to storyboard for our game. The game was broken into 2 parts, one consisting of the story and the other the gameplay. The story would have 2 screens, a dialogue screen and a screen to start the game, and the gameplay would also have 2 screens, the game screen and the game over screen, the screens following the order as described.      Next came taking our idea

     Lab 18 required us to use our skills from lab 17 to create a simple online calculator. Our calculator could be broken down to 3 main parts: a part to input 2 values, a part to choose the arithmetic done to the values, and a part to view the result of the transformation. I decided to make the input area first by setting up <form></form> tags. Within this form I opened 2 <input></input> tags with class attribute textbox, one for each number. Since I would need to retrieve the numbers input into them later on when working on JS for the site I gave appropriate id s to each, one being num1 and the other num2 . After completing the input area I moved onto the button area. I needed to make a total of 5 buttons, each for one of the 4 arithmetic function and modulo. To do this I opened up 5 <button></button> tags, setting the value attribute (which sets the text of the button), id attribute, and name attribute to the name of the arithmetic functio

     In our 5th WBL workshop we practiced our interview taking skills by doing mock interviews. During the application process of many jobs there is an interview stage, a very crucial part for candidates in the entire process. It is at this stage employers can best see how qualified a candidate is by asking questions face to face and seeing how well the candidate is able to respond. Just like how resumes are used to establish brand, candidates must use the opportunity of interviews to brand themselves to the employer as the best possible choice for a position. Resumes establish a candidate's brand in terms of skills and experience. Interviews confirm what a candidate established in their resume as well as establish a candidate's brand in terms of personality, allowing employers to see if  what lies behind the name and list of skills is a mature adult or a rude delinquent. Interviews can be stressful, especially when applying to big companies like Google and/or when competit