WEEK 10: ENTRY 3

 At my internship today, I gave my final project presentation to the firm’s Unix Global Team. Prior to my presentation, I did practice my slides a couple of times that morning to get over the nervousness and get more familiar with the flow of my presentation. So too, I was informed that the presentation was going to be held on zoom, so I made some speakers notes so that it would  help me remember what to say when I present. From my previous powerpoint presentation,. I learned that slides work best when I don't cram too much information - especially too much text onto them. 


Although the initial plan from the team was to present on zoom, it got changed 30 minutes before the scheduled time. The reason why this change was made was because unlike otherwise anticipated, all the employees in the Jersey City office that work in my team came into the office today. Usually only 15-20% of the team comes in on the same day to work. Therefore, I had to mentally prepare myself because instead of presenting on zoom and having to look at my speakers notes, I was now supposed to present in the conference room and so I lost that advantage. I kept a cool head because having practiced my slides numerous times, I was confident that I can present without my speakers notes. 


During my presentation, I was a little nervous in the first couple of slides, which could be detected through my voice and speed. But I gained momentum and confidence as I went further. I made sure that I followed the manner that I practiced and it worked pretty well. Among the audience in the conference room was my Vice presidents and the managing Director of the Unix/Compute team, which is the team I interned with. Through this presentation, I learned that practicing my slides before the presentation is always the best thing to do. I also learned that when you understand your project and know what your audience came to take away from the presentation, you are set to succeed. In my case, I made my problem statement clear and elaborate on what impact my project would have on my team. In the future, I look forward to incorporating the same technique to my presentations. 

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