#semester done

[redblackhearts]

Welp. This semester is over, now Christmas, new years, and seeing if I manged to get a job.

A lazy pop artwork I did to describe my mood.

At least now I will feel motivated to do art.

[sera-chyeah]

Ayyyy

Just turned in my last paper for the semester~~~~~~ 🎉🎉🎉

[treslecheslife]

I’m finished with school for the semester! Maybe that means more content from me soon!

[attimesiwonder]

Yay :3... I did it. Another step closer, but still quite far away. Slowly tearing down the walls I created for myself. But at least I know I want it, and that I can do it.

[officialmathilda]

BEAUTIFUL 88% on my final statistics exam FINALLY.

[softwareprogrammerhi-blog]

Git Branching

Version Control

In the ever changing field that is software development, we as software engineers/developers will have to learn version control. Version control is the concept that there exists software built specifically for the need of tracking changes made in the development process of code. All changes that are committed are linked to a specific person and a specific time. This way a development team can compare, restore, move about, and merge certain changes. One of the widespread software used it Git. GitHub offers version control to its users and aids them in ensuring that all code is kept up to standards.

Learning Experience

This semester at school has taught me that there are other valuable skills required to work in the engineering discipline of Software. When I initially began this semester I had no concept of version control. That is not something that was mentioned or really covered in most of my undergrad career. With minimal focus on this skill, I began working at a very large telescope project office. Once I began understanding what was expected of me, I came to the realization that this is a skill that is expected of Software developers. With this now in my mind, I began experimenting and learning more about Git and branching to ensure version control.

Teaching

Once I learned more about GitHub and how it worked I was tasked in my workplace to draw up some documentation for how certain tasks should be accomplished. I began this task and thought that I had finished it, however, after some thought and reevaluation I realized that I am not a professional at this and as I learn and evolve, so will my methods and documentation. I find it quite helpful to take some tutorials, such as: GitHub Branching following this link will take you to a #nifty website that’ll walk you through and draw diagrams for you so it is easier to understand. One thing I noticed about GitHub, if you plan on becoming someone who contributes to a project, you HAVE to know your version control.

Things I learned:

Pushing (not in a rude way :P)

Pushing is the act of pushing your changes to a local branch of code to a remote repository. I work in a collaborative Python environment with GitHub as our medium for storing scripts. Pushing to the repository from command line is a valuable tool that is used to update the team on changes and updates to the code. I learned this talent from this website. (I like making hyperlinks)

Syncing:

Another useful thing I learned from working collaboratively is Syncing. Any time you work in a collaborative environment, this is how you keep your local copy up to date with the current version. In speaking to the beginning of this post, version control is very important. Version control allows us to make sure that in a working environment everyone is on the same page and able to complete work in an appropriate way.

Wrapping Up:

To wrap up this blog post, I just wanna say that through this Python experience I gained a lot of new knowledge that I don't think I would've learned in the academic environment. CS 294 at University of Hawaii at Hilo, taught me skills that have made me into a valuable asset in a corporation that requires skills in GitHub.

[unsuccessfullydressed]

the fact that im done with finals means I can watch netflix without complaining about my pile of homework i wouldn't have done anyways.

[missmyseoul]

And the jury is out

My final grades have all been posted, and well for all my complaining I didn’t do too badly. I got 3 A’s, 2 A-’s, and a D+. For taking 18 hrs, it’s not horrible. Only the GPA killer of Statistics classes at my university really suck, both professors that teach this have a like 50% fail rate, at least I don’t have to retake the class because a D- above is passing. It also probably wasn’t wise to take Finance, Statistics, and Supply Chain Management all in the same semester, since all deal with numbers and formulas, and scm and stats with lots of quantitative reasoning.  All in all I’m fine with my grades though,  and can’t wait to go home for break tomorrow.