WEEK 8: ENTRY 2

 Ever heard the saying “Bad programmers worry about the code. Good programmers worry about data structures and their relationships?” Well, it is very much true in my scenario at my internship today. As a new Go programmer, I was much worried about writing the code and making it work as it should. I worried less about the code structure, but my manager is very worried because my project would be used in production and if someone else is going to work on it, they shouldn’t struggle to read and understand my code. Therefore, I was tasked to refactor my code. When I say refactoring, what I exactly mean is grouping my different functions into different directories and having different Go files. Since I have multiple logic for different API calls and data manipulation, I was required to arrange these logics and API calls into different directories and files. 


Although both my Elasticsearch API  and BigQuery API  calls used the same http client, the API responses in both cases are in different data formats. So too, the functions I wrote to make these API calls used different packages and functions to read the data from the API. As a result, I made a package directory, which has two separate directories that have Go files for both API calls. Prior to today, I used Python import statements to call other functions; however, Golang imports are quite different. Unlike python imports Golang imports require you to import the package that you use in other directories. In addition, the way we pass the return value to another function is  quite different. I struggled with this because I have never done these Golang imports. Passing a function’s return value requires you to also pass in what the data type of that return value is. 


I can conclude that I gained a better understanding and insights on how to pass parameters to totally different functions in a different directory. Besides, I also now appreciate the fact that I am more fluent with troubleshooting errors with Golang print statements. However, I am still slow in resolving issues when I encounter them. I intend to work on my pace and troubleshooting speed faster than I am currently doing. I plan to google the right thing and read documentation on stack-overflow answers rapidly.

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