WEEK 1: ENTRY 1

 Prior to my first day of Orientation, I read a couple of blogs and documentations on Goldman Sachs divisions and its main operations. Thus, I was pretty confident that I had an idea of the divisions in the firm; however, after the first session of my orientation, I must say that my little knowledge about the company was not quite enough compared to what I learned about the firm. The company has numerous divisions and each division works hand in hand to achieve the firm’s main objective. For me, the first days have been very eye-opening moments because I was not only amazed by what the company does in terms of Business, but what they also do with Engineering is pretty awesome. I had the belief that it is mainly Finance and Marketing driven, but with what I have learned thus far during the orientation, I must say that the firm is heavily utilizing AI, Big Data, and Cloud computing to make sound decisions and improve the systems in the company.  

Besides, I was met with another surprise with the “Marcus” saving accounts ideology.  I have always thought that  the firm only focuses on big investments and acquisitions.  I did not know that the company also allows customers to open saving accounts, where they can both deposit and withdraw from. This savings account is referred to as “Marcus.” I should have done more reading and findings before drawing to the conclusion that big firms like Goldman Sachs are only focused on big purchases and business dealings. Overall, I was very fascinated to learn how the firm utilizes engineers in each division to acquire the divisions’ objectives and Key results.  My first two days have been enlightening. Debunking the myths I had about the firm has been satisfying. Next time, I will try to look into the bigger picture and do my assignment well before believing in people’s concepts about a firm or company like Goldman Sachs.

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