WEEK 10: ENTRY 2

 At my internship today, I worked on finalizing my powerpoint presentation for my final Global Team presentation. For the powerpoint slides, I was supposed to follow the generic engineering slide template format. Therefore, I requested to have a look at the previous intern powerpoint slides so that I can have an idea on how to structure and outline my slides. After receiving the design template, I was surprised that it had little or no graphics. For me, the design template was not appealing and had less standardized colors and styles. As a result, I decided to incorporate more graphics and standardized colors to my slides. 


Although I used the designed template I was handed, I tried to only include necessary information as well as used colors that contrast and complement each other. So too, I made sure that my powerpoint had a coherent flow of ideas. For instance, I made sure that with an introductory slide, an agenda slide, an overview of what my project is, the problem my project is trying to solve, the solution my project offers etc. By arranging my slides this way, I can capture my audience’s focus and develop that sense of focus throughout my presentation. Another component that I had to keep in mind was the time allocated. As I have had a previous experience at Berea College last year when I presented over the allocated time, I was making sure that I do not repeat that mistake this time because I do not want to bore my audience. Thus, I made sure that I limit the information to essentials. 


After putting all my slides together, I had a walkthrough with my manager, who gave me some critique and suggestions on what changes were most essential to make. One of the points that he made was that the traditional style within the engineering team powerpoint was to make sure that the slides were less colorful and more content driven. I used this feedback to make all my slides’ titles less colorful and uniformed as well as lessen the graphics I had put on most slides. Generally, I learned that with their recommendation, my slides were supposed to be simple and less wordy. I also learned that to make sure that my audience not only keep watching my slides, I should use less destructive graphics and more simple diagrams to explain my logic. Therefore in my next powerpoint presentations, I intend to use these techniques and make simple but yet easy to follow slides.


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