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 worked, I was still receiving some “undirect” errors from my server side. I must confess that at this point, I was so overwhelmed and discouraged because it seems I have spent a whole week on the same issue, which is not a good sign. However, my manager said that unlike other teams, my team focuses on infra and not just the implementation of the design. I have been working on the deployment setup in order to help me understand the basics behind infra. 

So too, I had a one-and-one informal feedback with my manager today to see where I’m doing well and where I need improvements. He outlined that I should improve the pace at which I work as well as my troubleshooting skills. He suggested that I should always try to figure out the issues before asking for some assistance. He also mention that I shouldn’t compare my project’s timeline to other teams because we are working on totally different projects and structure. It struck me hard but I am looking forward to using this constructive feedback to improve and adjust to the flow of the team, while also developing a great sense of understanding of the tools we are using at my team. Therefore, I intend to dedicate my whole weekend revisiting all the commands and processes we used this week because it will foster my understanding more. 

Comments

Post a Comment

Popular posts from this blog

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 p...
Read more

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 becaus...
Read more

WEEK 10: ENTRY 1

  At my internship today, I worked on cleaning my code and handing off my project to my team. Having worked on this project for the past nine weeks, it felt so satisfying and fulfilling that I had the opportunity to finally meet the project deliverables and hand off my project. My code was not the best written code because it was the first time programming in Golang for me; however, now that I looked at how much logic and functionalities my codebase does, it is truly intriguing.   So what does it really mean for me when I say clean my code. Well, as I mentioned earlier, this was my first time programming in Golang. Therefore, I did have a lot of print statements for debugging. I integrated these print statements because they helped me to easily find bugs as well as know the stage of my logic. Another code refactoring I had to do was removed commented out chunks of code. Since these code was no more needed in my codebase, I had to get rid of them so that it’d be more organized ...
Read more