Career Experience as an SWE @ Apple Proactive
Week 2
This week I learned more about how to get the accesses I will need. There were many errors, permission issues, configuration failures, version issues while I was trying to get Kube and AWS@Apple up and running; most of which I have no prior training on and experience with. My perseverance is stretched to great extent. I’ve reached out to several slack channel communities for help and received many support, hints, and pointers. I’ve learned how to use command lines in the terminal to solve some of those issues. I’ve also understood better how security and level of accesses are managed by Apple internal.
For Kube, I built a simple HTTP service written in Golang, containerize it using docker, and then transfer it to the Apple repository. Along the process, I learned about YAML file type, docker file, docker images, Artifacory API keys. Intermittently, I took my time going over the documentation and searched key technologies that I will need to continue using in the future. My goal was to understand what those technologies do and why the team has decided to use them.
Moreover, I had great joy attending one-on-one meetings with many team members at Proactive. It was wonderful to get to know them a bit more on both professional and personal levels.
what I learned
- AWS@Apple basics
- Team members one-on-one
- Kube basics
- Docker (yaml, docker file, docker images, containers)
- ACS Artifactory
- CLI command lines
- Using Slack channels to get help