WEEK 1: ENTRY 2

Today at my internship, I was tasked to set up my working environment.  Just like many engineering setup, the environment setup today was specifically based on the tools that I will use throughout the internship to build my project. The tools I set up were basically the Integrated Development Environment, IDE: to write code on; Github: to commit and push the code, and the test suite dependencies. Although I had prior knowledge about the Github environment and the IntelliJ IDE, I still struggled to set up the environment and run a simple “Hello world” Java code. The reason being is that my prior experience with Github and IntelliJ has been that I only understood Git commands and installation of simple packages on the IntelliJ IDE respectively. 


During this setup, I learned that there is a lot more that one can do with Github: not just pushing code to it. For the first time, I learned that there is actually a deployment environment related to Github called Gitlab, and there is a core difference between these two. Unlike Github, Gitlab has Continuous Delivery/Continuous Integration(CI/CD), and DevOps processes built-in. You might wonder what Continuous Delivery/ Continuous integration is, but it is fine because just like you, these terms were just phrases I heard before and barely had any idea what they meant.  In simple terms CI/CD means automatically and continuously testing, building, and releasing code changes to the deployment environment. I was startled by how fast and efficient the Gitlab CI/CD feature is used at my workplace. 


Another insight I got today was how an IDE, like IntelliJ can be connected to a deployment environment like GitLab. Unlike how I used to run git commands to push my code to a git repository, the IntelliJ version I used today had all the git command features with just a click of a button. The checkout, add, commit, and push git commands are all built-in into the IntelliJ environment. One does not have to type these commands. These cool features and tools made me question how I used to do things to be honest.


In general, I must say that developer’s tools are changing rapidly and there are many versions and ways that these tools are used. Today’s session was a mixture of both realizing and getting reminded that in tech, I must have an open mind on how things are set up and why they are set up that way. There is not only one way of achieving the same goal.

Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more