Quickly Mastering Proprietary Technology
When I joined Series, the team was small and the company was developing and testing new proprietary tools that would help non-technical people to easily implement gameplay features.
In approximately one week, I had to learn and master said tools in order to fully support the team.
The tools were not mature yet and I had the opportunity to help test and improve them as an early adopter.
The narrative team was also not fully familiar with them. I became a key link between the teams, teaching and helping them understand the issues faced.
The tools and concepts included:
- An Ink-based web tool for writing games with features such as launching and debugging the game, and compiling Ink in real time.
- The connection between the Unity-based codebase and the Ink content.
- Content (images, sound, text) management on both sides, best practices for naming, organization and integration.
Becoming a Trustworthy Multidisciplinary Team Player
Given my technical background, I was able to contribute much more to the team than design expertise and feature integration.
I became a valuable part of the team, as I was able to detect a bug on the user side, trace its full path back to the Unity code and push a fix for it, without taking up valuable time from writers or engineers.
I also coordinated and organized dedicated communication channels via Slack or meetings to address any writer's issues in real time, unblocking them at least twice as fast as before.
My role became a bridge between the Engineering and Narrative teams, going beyond facilitating communication. I participated in both writers' rooms and Engineering meetings and symposiums and was able to bring the non-technical team's
vision to the Engineering Team, achieving a smoother transition and knowledge transfer from one team to the other.
Feedback and Contingencies
The games were developed for Netflix Games. Each milestone brought back feedback and issues to address.
This was an extremely valuable experience in responding to client feedback and new requests, reacting quickly to unexpected issues and coordinating with the whole team to deliver as expected.
Some of the games suffered from rare performance issues or bugs that only occurred on specific phones. I was
also able to be part of the debugging and testing of said problems.
This allowed me to learn a lot from my peers and seniors in terms of how to approach client revisions, how to deal with contingencies,
and how to keep the team's morale high, even under sometimes demanding conditions.