Tuesday, February 2, 2016

CST 336 Week 5

Week 5

This week we learned about storing user data in sessions (specifically for logging in and out of a website). It was a very quick intro and very simple. We were assigned reading from chapter 12 (titled "Working with Cookies and User Sessions") of Sams Teach Yourself PHP, MySQL, and Apache All in One. The lab assignment was nice this week since we just added a log in to the website we did last week. I'm glad it ended up being short because it allowed me to spend more time on the team project.

I think my team has gone beyond what the assignment detailed, which is good, but it also meant that I have spent time on certain functionality that didn't meet the assignment requirements. So, this project has taken longer than I was expecting.

Below are my assignments for this week.:

Tuesday, January 26, 2016

CST 336 Week 4

Week 4

This week we were assigned to read chapters 15 and 16 from Sams Teach Yourself PHP, MySQL, and Apache All in One. The topics covered basic database design and basic SQL statements (SELECT, INSERT, DELETE, etc.). There are three relationships that help relate data in databases: one-to-one, one-to-many, and many-to-many. These relationships help us to better maintain our databases. The chapter assigned used students as examples for these. This is very useful information, but I would really appreciate new examples. Relating students to classes and professors is a very tired example in academics. I find that this example topic leaves me bored and disinterested.

We've also began our first team assignment of the semester. Our team has been a little late to the start, but I'm sure we will complete it fine. I'm glad we have settled on an idea and started building out our tables.

Below are my assignments for the week (team assignment should be posted next week):

Tuesday, January 19, 2016

CST 336 Week 3

Week 3

This week we covered HTML forms and PHP arrays. We were assigned the videos from section E of Atomic Learning's HTML5 & CSS3 - Basic Training course, videos from section E of Atomic Learning's PHP Basic Training course. I really enjoy these videos. They're extremely insightful and it's easy to follow along. Coming up with what I will do each time to fulfill the assignment's requirements each time is challenging. However, I am very excited about my assignment this week. Since there's been a lot of hype over the large Powerball winnings, I've created a generator to decide on numbers for your Powerball ticket. It ended up being a lot of fun.

Below are my assignments for the week.

Saturday, January 9, 2016

CST 336 Week 2

Week 2

This week has been focused on creating webpages with PHP. We were assigned reading from the second chapter of Beginning PHP5, Apache, and MySQL Web Development. We were also assigned videos from Atomic Learning's PHP Training course.

For me, this week and last week are basically once since I messed up on the start date for last week. The projects were pretty basic and we've basically been writing the HTML inside of the strings in PHP. This is my first time working with PHP and I am getting a grip on it, but I am still feeling like PHP is pretty messy and it is complicating my HTML. I get the feeling I'll learn a bit more in the upcoming weeks that will help me clean it up. I'm also going to begin looking at various PHP style guides to better understand how companies keep their code base clean and easy to read. So far, the example videos and code snippets don't appear to have much or any code style discipline. Python, which was used in the last course, has a very distinct style guide. It doesn't appear that PHP does.

We began creating some very simple HTML pages with PHP. Below are my assignments for this week.

Friday, January 8, 2016

CST 336 Week 1

Week 1

I'm a bit late on posting this since I thought the assignments for this week weren't already due (they were due the day after the class officially began and I had gone out of the country during the scheduled break), so I'm late on all of my assignments for this week. The week 2 post will follow quickly after this week 1 post. This week we covered several components that can, and often do, make up a website. We were required to read O'Reilly's Learning PHP, MySQL, JavaScript, CSS & HTML5 Chapter 1 Introduction to Dynamic Web Content and follow along through several videos in Atomic Learning's HTML5 & CSS3 - Basic Training videos. Reading through these were pretty simple for me since I already understood these basic concepts. They are really good things to understand and review though, so I read through all of the materials and watched all of the required videos.

We also created some very simple HTML and CSS webpages. One of them was more free form and the other appears to be our home page where we will link all of our assignments from. Below are the webpages I put together for these assignments. Note that the second can be accessed through the first.

Monday, December 14, 2015

CST 205 Week 7

Week 7

This week is the final week and it's gone pretty well. My team executed the final project nicely, even though we usually end up working on it right before the deadline. I'm pretty happy with the end result. We made a memory game and redrew the squares of an image to help guide the game. The user makes their selection with input in JES. The labs were quick and easy this week, too. It was very nice. In this course, we learned how to manipulate sounds and images. I found sounds to be the most useful, since I've never considered how to work with sound before. Future students will benefit from understanding these things as well. It's useful to understand the best way to save images and audio for your use case. My general advice for future students in this course is to do all of your individual work as soon as it is assigned, since (at least in my group) it is unlikely you'll be able to meet with your group then. When the deadline approaches, you don't have to worry about it. If you don't understand something, I find that my best resource is YouTube and Google. Use them. Sometimes seeing someone else do something or present it in another way can be extremely helpful.

Assigned Readings

How to Get a Job at Google, Part 2 by Thomas L. Friedman (New York Times) 

This article spends a fair amount of time explaining how going to college is worth while and can build a lot of character. In part 1, I believe they had suggested that college may not be for everyone and that many companies, like Google, hired employees without college degrees. This follow-up article feels like it is defending college degrees based on responses to the last article. The gist is that students that work toward a more difficult degree and come out as a "B" student are more valuable than those that come out out easier degrees, like Communications, as an "A" student. Because the student had to work really hard through their career, they show their dedication and problem solving ability. In a career, they'd be able to come up with solutions (and not just have the problem memorized).

Internal Problem Solving Guide

The first point was to read Mind Tools' What is Problem Solving? article. Apparently, there are several named ways to solve a problem. In the article, they describe a basic four step problem solving method where you compare routes you've come up with. The other methods are called the simplex process, the appreciative injury process, and the soft systems methodology. The internal google document provides questions that can be asked to clarify what the problem that you're having is and lists a few ways getting the solution can be approached. The best solution I saw in the document was to have someone else review your work.

Sunday, December 6, 2015

CST 205 Week 6

Week 6

This week we covered lists, dictionaries, reading files, and good programming practices. Python has some nice features for their lists, like joining two together with a "+". So, [1, 2, 3] + [4, 5, 6] will be [1, 2, 3, 4, 5, 6]. Also, it's really neat that the values in a dictionary can be different for each key. It's extremely flexible.

The projects this week have been pretty tame. One lab was an individual lab and the other was a pair programming assignment. Both of them were pretty straight forward and simple. We began working on our final project this week, too. My group is going with a memory card game, so that we can use both the text-based game requirement and the image manipulation requirement. I think we're off to a good start so far and I'll be looking forward to finalizing it next week.

Monday, November 30, 2015

CST 205 Week 5

Week 5

This week has been pretty relaxed (maybe because it was Thanksgiving?). There wasn't nearly as much work as there has been previous weeks. The readings were geared toward debugging. All of the assignments were team projects and basically were compiled into one primary game. The game is a text based choose your own adventure style, like Zork. The idea is pretty simple, but we went through a few different ways to implement the project to make it easiest to develop on. As usual, meeting with the team has been pretty difficult... but we figured it out in the end. I still think we could use some guidance on pair programming. A team of 4 all typing at once in codeshare.io is a bit crazy and I think everyone would benefit from learning how to pair program properly when remote (one "driver" and more dialogue). We have the code for our game on our team's GitHub Adventure Game Repository.

Assigned Readings

Silicon Valley's Race to Hack Happiness by Emma Seppälä, Ph.D (Huffington Post)

This article discussed how people and companies are beginning to create or hold competitions to create applications to help with mental disorders and make people happier. The author explains that depression has increased and more people are looking for ways to make themselves happier, like going to yoga, reading self help books, and now looking for applications to boost their mood. These applications seem fine. Using technology for things that could benefit people seems like a good thing. However, there wasn't any data to back up if these applications are helping or not. Because of this, I'm hesitant to say that this is a good route to take to come out of depression at this time.

Monday, November 23, 2015

CST 205 Week 4

Week 4

This week the majority of our assignments have been focused on sounds. Becoming familiar with sounds and how they're digitized has been pretty interesting. I think I still need to practice understanding the correlation between bit depth and the value. Aside from the sound assignments, the rest of the assignments were focused on string manipulation and access in python. String manipulation has been pretty straight forward since it's similar to other string manipulation functions in other languages. However, splicing and splitting strings is a bit different in python (with the string[:3], string[3:], and string[3:3] syntax). The paired programming labs were a bit better this time with encouraging them to be done together, as a pair. Also, we had to wrap up our midterm project this week, which was creating filters on photos with certain themes. We had to do one that was CSUMB themed and one that was up to our own discretion. I chose a Buffy the Vampire theme. I'm pretty happy with that decision.

Assigned Readings

The Employer's Creed from Op-ed columnist, David Brooks (The New York Times)

Many companies hire people based on their (almost perfect) resume. This article asks that employers look for different things in potential employees, like obstacles they may have overcome. It suggests that these companies should prefer candidates that are different from the rest and challenges them to not follow the social norm of hiring practices. This sounds great and realistic, but that's just not how most companies are hiring (aside from focusing on the cover letter). I do think that you have to have that characteristic or special thing you can bring to a team in order to stand out from the crowd and get a job.

Sunday, November 15, 2015

CST 205 Week 3

Week 3

This week we learned about git and worked in our teams to create cards for Thanksgiving. I use git and GitHub regularly at work, so that hasn't been challenging for me to pick up. The most difficult thing about this week is working in the group with little direction on how to work together as a group. Also, the assignment doesn't feel geared toward collaborative pairing. We were supposed to create a card for each member of our group, leading us more or less down the path of creating our own cards. If we were all forced to create one, together I think it would have been a different story. It's also nearly impossible for all four of us to be at the computer at the same time. We also have a midterm coming up, but it seems like we will still be applying the same kinds of methods we've done up until this point, so it should be pretty straightforward.

Assigned Readings

Pair Programming (Wikipedia)

The Wikipedia page for pair programming currently describes pair programming as having two people working on one computer. the two people switch off being the "driver" and "navigator". The driver writes the code and the navigator comes up with various ways to do operations and acts as the extra set of eyes for bugs. It also details some of the benefits and studies done on pair programming. I have pair programmed quite a bit in the past and love the idea of it. Unfortunately, this course hasn't yet defined any way to go about setting up meeting times and student environments (tools) to facilitate remote pair programming. Instead, we're being directed toward a collaborative git workflow. It's extremely frustrating (from what I'm seeing) for the students because the reading we're directed to provides guidance on pair programming in a situation where the students are in the same room.

Facial Recognition Systems Turn Your Face Into Your Credit Card, PIN, Password (The Huffington Post) by Betsy Isaacson

This article briefly describes that it's possible for computers to recognize and distinguish human faces. A startup company, called Uniqul, released an ad full of hypothetical situations where they showed consumers that could pay with their face. So, there was no real transaction and just a button that the user clicks that says to accept the charge. The company is hoping to develop the facial recognition technology to do this. I'm not really sure how this relates to this course, but I guess it is showing us what we could potentially do down the line.

Autism And Google Glass: Teen's Software Could Help Users Recognize Emotional Cues (The Huffington Post)

Sension is another facial recognition product. This product uses faces to track and test the level of engagement an end user is experiencing and to provide a new way to play video games. This product ended up having an unintended application, which is to recognize different emotions that people are conveying at the end of the camera (found useful when dealing with autism). I'm also not sure how this relates to what we've been studying, but we will see.

How to Get a Job at Google (The New York Times) by Thomas L. Friedman

Google had nontraditional hiring practices. As a programmer, many people will go further if they can learn quickly and face challenges well. I know this is the accurate because I don't have a degree and work as a programmer. There aren't too many people that are in the field without degrees, but I can attest that the ones that are work very hard. In relation to this course, I believe this article was better suited for the ProSeminar course and doesn't really apply to a multimedia design course.

This is the Internal Grading System Google Uses for its Employees -- And you Should Use it too (Business Insider) by Jay Yarow

This is another article that seems to be a better fit for the ProSeminar course, but it basically explains how Google grades themselves on their own tasks. Prior to a particular set of time, they establish several (less than six) quantifiable goals. They are graded on a scale of 0 to 1, where 0.6 - 0.7 is the ideal result. A full 1 would mean the goal was too each and closer to 0 would mean that the goal was too difficult. Perhaps this was a subtle suggestion that we should try out Google's Objectives and Key Results (OKR) strategy for ourselves.