This summer I was tasked with updating my team’s rails web app api from version 3 to 4. This included improving and adding to outdated api documentation, bringing the api to HATEOS standards, and finding a new JSON presenter as the old one was slow and lacking support. This project gave our users a better experience as documentation, performance, and routes increased, helped our support role not need to handle api questions as often, and in the future our UI can use the api to render from.My favorite part of this project was the design decisions I was given, that I don’t get at college. I was asked to find and present to my team the best JSON presenter for the api. After researching I found fast json api to be best for our web app, replacing rabl. I also was able to become an expert using postman, as I was able to build out collections for teammates to use in the future for our web app. Lastly I learned about the a new standard for api documentation in HATEOS to allow the user to use the api in a way that one would use a webpage. Testing and working with the team was a lot of fun implementing this.

My team was responsible for maintaining and enhancing Cerner's inhouse webapp for datacenter automation and management. This was a Rails webapp with an MVC model setup. I made multiple UI, datatable, and logic features that were tested and put into production over the summer. One of the tasks I enjoyed most was being given the time to learn GO lang and using it to add to and build new features for the GO SDK of the webapp. My code was subject to code reviews and required Ruby unit tests to test the features.

Focusing on two projects this summer. The first being a smaller project automating slack messages when a ruby gem job fails creating a JIRA issue. The other setting up VLAN switching service from clients in a web app my team upholds. I added VLAN switching to the UI and API of this web app using languages such as ruby on rails and stimulusjs.

After spending the school year as a Cerner Scholar I was transitioned to High School Technical Intern for the my second summer. I stayed with the same team I had been on as a Cerner Scholar during the school year. I will be updating server software and processes, in order to maximize up time. This includes setting up rubocop standards, vault password manager, and open postgresql monitoring.

As I ended my summer as a High School Technical Intern, I went back to high school for my Senior year. This meant I would re-transition to a Cerner Scholar so I could stay with Cerner during the school year. As I went back to being a Cerner Scholar I switched to a new team to gain a greater view of Cerner and different parts of Cerner. The projects I worked on were focused on speeding up processes and limiting downtime. I improved the Server request system, made a password storage system, and did many code reviews for my team. This required me to have a strong understanding of Linux Servers and coding format.

After spending the school year as a Cerner Scholar, I was transitioned to a High School Technical Intern with the same team. I continued working on a KPI for my team as I did in the school year as a Cerner Scholar. This project required me to have a complex understanding of JavaScript, CSS, HTML, AJAX calls, and Jira API. The KPI allowed my team to better view roadblocks and issues they were having with projects allowing them to more effectively use their time.

I worked to document third-party tools used by my team, build database information decoder, and started building a KPI for my team which I continued in the summer as a intern. These projects required me to have a complex understanding of JavaScript, HTML, CSS, AJAX calls, Jira API, and increase my knowledge on Open Source/Third Party Tools. This was a internship during my Junior year of high school, I would go to school half the day and spend the second half at Cerner.