Summer 2015 So F ar

One of my goal this summer is work on my project, which ended up with me taking a long detour in both brushing up and learning new skills in JavaScript, JQuery, Ajax, PHP, MVC, and OOP. There was a lot of reading, online video/school, and coding. I have sadly ddiscovered that I have learned more about Ajax in a 2-days self-study using Treehouse video and books than I did a semester of class, but hey, some classes are better than other. It’s been good, although I ended up pushing back my C and Anduino learning.

IT network self-study has been going well. Since I am taking the same professor as I had in my Introduction to Networking for the next semester course in Network Security, I feel that I should brush up on my network knowledge. When I took my first network class over half year ago, I was new to CS and have no idea what is going on. I am half-way through re-reading my books and notes. Now that I have a lot more experience, it makes much more sense, and I feel more comfortable about jumping back to a networking class this Fall.

In term of Fedora, because of that fact that half of my self-study files are local, I lacked a reason to even turn on Virtualbox. But no more. Most of my learning files and even a good portion of my project files are now on Dropbox. I installed both Dropbox and Sublime Text on Fedora, so I can now do most of my coding and studies in Fedora!

Although, Fedora have problem waking up from its sleep in Virtualbox. It would either remain the black screen of death or refuse to let me type anything. In addition, I am consistently clicking on command-C instead of control-C. In Virtualbox, control-C actually exits the Virtualbox out of its full-screen mode instead of copying text. As someone who loves shortcut key and types pretty quick, it’s driving me a bit crazy. I pretty much do a command-key shortcut every 10 minutes when I started using Virtualbox, then when I do return to my Mac OS, I would do the opposite! (As in using control-key for shortcut every 10 minutes). For the first time in my life, I curse my ability to type so quickly…

Open Source Comes to Campus @ CCSF and my first GNOME in Mac Installation

The first time I know that I was using open source was when I first got my Macbook, which did not had Microsoft Word. Mac MS at the time was more expensive than the PC MS. So… I downloaded OpenOffice instead. The second time was when Adobe Creative stop working for the new Mac OS – less than a year after I brought it. Instead of relying on a product that was clearly unreliable, I downloaded GIMP. It’s been 7 years, and I have never look back.

When I learned about the Open Source event coming to CCSF from my friends on Facebook, my reply was “That sounds fun! I am in!”.

Besides, there is free breakfast and lunch. What college students says no?

The talk started with explaining what open source is and showing logos of known open source projects. The presenter, Asheesh, joked that the logo was “Probably the most things people remember about Openhatch” as he waved the penguin(?) sticker. Mental nod here – I know the penguin before I know OpenHatch.

He went onto introducing ways to contribute. One of the ways for new coders was simply to point out issues. The presenter then went on to Issue Trackers and communication methods. When he opens the IRC program window.. wow, instant flashback! It was a chat room, and I haven’t been to those since middle school.

I went in the workshop expecting talks about programming, but instead the first demo was a chat room. It was very telling about how open source works. One of the greatest difference open source has with private companies, from what I experienced in this workshop, was its sense of community despite diverse locations of its members. A company strives to find the ideal personality in the same location, whereas open source  projects is about those who can find them on the virtual realm and is offer their time and dedication.

After some laughs about the chats (the people in the chat room realized quickly a class was going on. Silly conversation and jokes ensued), we moved to some Github work. While I have been using git and Github to record the status of my self-studies and side projects, I have never had the chance to collaborate there. It was the first time I forked and the first time I pulled an updated project. I found it pretty awesome to see how, when the project was merge and my submission contained “Fixed #5”, the issue #5 that I fixed would close on its own.

After that, the mentor went around the tables to talk about their open source experiences. We heard stories of how it begins, what they learned, and what got them there. The first person talked about the importance of knowing how computer works, not just the language. One talked about his love of the open community. Another talked about how program vulnerability has a ripple effect on private companies that uses open source technology. The final person talked about how open source can solve real life problems. Their stories varies, but they have this in common: in some ways, programming and open source has changed their life.

Then, it is the last session – projects! The mentors summarized their projects and then find an area to stand so we can, as a mentor joked, “flock” over to them. I debated on my choices. In the end, I decided to went with one where two mentors teamed up to talk about Ubuntu technology and creating new OS. The idea of creating OS is just too cool to miss!

The interface and customization of GNOME was beautiful to watch. I enjoyed the discussions behind the creation and community teamwork of GNOME, and how it interacts with and affects third party distributors like Ubunta and the two other OS. They showed us various projects and widgets that could use some help. In the end, I installed GNOME via Fedora and VirtualBox on my Macbook for the first time. It was ridiculously easy after the agonizing experience I had with installing VM on our school computer for my Linux Admin class, though the later was probably so complex because they want us to know the steps and details. Plus, I don’t have to worry about remote access for this one!

This is purely about exploring the various features of the system, which I can’t wait! Contributing to the GNOME can be simple as just exploring and pointing out bugs. For those who are more advanced in their programming skills, they can help with solving existing issues. The mentors recommended for those whom wanted to learn more. For now though, I am probably just going to try the OS out and see what happens!