Evaluation and Conclusion

Evaluating my internship and what I have learned.

Project Evaluation

The initial design challenge was the following:

"Implement a cloud-based pipeline that can provide concrete feedback on the realism of (a) provided image(s) or video(s) of an AI-generated avatar so that the developers of the avatars can verify the applicability thereof in social situations and ensure continued immersion in the interaction."

This was the goal I had in mind when I created the various prototypes. As research and development continued, however, the emphasis shifted: as I do not have sufficient domain knowledge or proficiency in data analysis, it is better to focus on what I do know. In this context, that is setting up an environment in which such an analysis could easily be facilitated. In other words, a fitting architecture to support the project.

Once this change had been made, I took a deeper dive into what kind of services Azure has on offer to support a use case such as this. By extensively researching, seeking advice from colleagues and some trial and error I am now confident there is a good platform to expand upon in the future. The goals of the initial design challenge have been reached, while putting more effort into making sure the pipeline makes extensive use of cloud-based services. It is well-documented and set up in such a way as to be easily expandable. Furthermore, the client was informed every step of the way. Because of this, I believe the design challenge has been sufficiently met.

Personal Evaluation

Here, I will go over my favourite and least favourite parts of the internship. For more information on my specific learning goals, see the specific articles (technological skill, decision making, independent development, career prospects).

The Positives

There have been few projects where I had the opportunity to be this free and creative. The core goal and the fact that the pipeline was supposed to be cloud based was set in stone. Aside from that, it was totally up to me, my research and preferences. This gave me the perfect opportunity to learn new languages and technologies.

The fact that my input was seen as equal to the input of more veteran developers or teachers was also very refreshing. It truly gave me the feeling that I have come far since my first semester at Fontys. The feedback I received was great and helpful, and the project in general was very "cool" to be a part of.

Meeting with other interns gave me a great feeling of comradery. Helping others out or simply hearing about their projects felt like a nice break from my own work, and helped me feel like I was in less of a bubble. Furthermore, these meetings also allowed me to show a more team-oriented side of my skillset. This lead to me trying for a job at Fontys.

The Negatives

The main downsides for me were twofold: the lack of focus on games or game design, and the lack of cooperation with BUAS.

The former is quite straightforward: though the project is in line with game technology and supports a game technology focused project, my contribution to it felt far removed from that at times. It felt like a software engineering project. Luckily, I enjoy this too! However, more focus on game technology would have been more enjoyable.

When the project started, I imagined BUAS to be the main client of sorts. As the project progressed, however, it became evident that this was far from the case. This culminated in my first meeting with them being quite far into the project, and them seeming rather disinterested at that time. I believe if there was a closer cooperation with them, it would have lead to a product more closely tied with their development pipeline. Luckily, the pipeline is modular enough to facilitate their shifting demands, however.

Conclusion

All in all, the internship has been a great experience that has given me a better picture of my career opportunities while giving me the freedom to be creative and work on an innovative project using technology I was not familiar with.