WEEK 5: ENTRY 1

 I have not felt so satisfied achieving a milestone in a while like I did at my internship today. It feels so great to finally have your code do what you envisioned from the start. So how did this start? Well, a week ago, I started my Kubernetes deployment, Gitlab CI/CD integration and Go HTTPS GET Request. This deployment was meant to be the foundation to my HTTPS Go Get Request call. However, my CI/CD pipeline was failing and the debugging was rather difficult because I was unable to see my logs from the PUTTY CLI. And even after seeing the logs, it was still not giving much helpful information to where the error was coming from. What was the issue? Unfortunately or fortunately, the error was not from  the codebase I wrote. It was the company’s packages and libraries that were not up-to-date. As my buddy was helping me debug, he was able to point out that we were using the wrong version of the packages all this while. 


Besides, I felt a great sigh of relief because I was so overwhelmed and worried that I was not understanding what I was doing and that the error was all from the code I wrote to make the GET HTTPS request. I must say that I learned from the debugging process that the most important thing in coding and development is to focus more on figuring out the  error rather than overthinking about why you are having the error.  So too, I gained a better understanding and appreciation of how important it is to be patient while coding. The debugging process also gave me more  understanding of my codebase and what each code block is trying to achieve. It might sound cheesy but having worked with the Kubernetes deployment, GitLab CI/CD, and GO programming HTTPS Get Request at the once to achieve my goal, I must confess that I am now more confident and recharged to continue with the next milestone of my project. 


So what is next? Well, it has just been half-way to my internship and it has been both an educative and restructuring moment for me. At least this issue I just resolved has given me a huge heads up on what it is like working in a corporate company and how different the expectations are daily. I am looking forward to developing a more open-minded and relentless mindset when I am faced with errors.  In addition, I intend to work more efficiently and improve my pace because time is limited and there are deliverables that need to be met.

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