Philip Rowlands Email and Phone Number

Working on my first commercial game (and first Godot project), Turret Baffler. This is a first-person shooter which involves helping an NPC get past turrets, cameras, and other obstacles.Free demo available from GameJolt and Itch.io:- https://gamejolt.com/games/turret-baffler/953045-https://aceade90.itch.io/turret-baffler

I was moved onto a SaaS social media processor that was deployed to Azure, and was heavily based around NodeJS/TypeScript microservices with two React-based administration portals. There was also a Ruby on Rails backend, but I rarely touched that. Key contributions here include:- Refactoring the React portals to remove or hide unwanted elements and to add a Content-Security-Policy header to hinder XSS (Cross-Site Scripting). I had no prior experience with React before starting this.- Integrating Datadog metrics with our Node microservices, working with another developer to provide a common wrapping library and documentation for our metrics.Between November 2021 and December 2022, I worked on the hybrid predecessor to this service. My main tasks/achievements here were:- Updating an SNMP monitoring service to use SNMPv3. The service had no documentation and required significant refactoring to address numerous defects. Despite this and my lack of prior Python experience, I was able to deliver a functioning service in four months. - Spending 3-4 months manually filling out copyright/licencing details in Black Duck for approximately 2500 npm packages across the entire application to obtain legal approval to deploy the application. This annoyed me enough that I have subsequently changed my JavaScript package manager to pnpm due to it having a built-in command to list every licence the application is using.- Researching the Google Play APIs and creating a proof-of-concept for a potential microservice that would allow a contact centre to poll for reviews on Android apps. Due to limitations with the Play APIs, this ultimately never went anywhere.Almost everything I worked on here required manual testing due to lack of time to get any automation working.

Still working on Avaya Oceana digital contact components.- Researched language detection with Apache Tika for the web chat API, allowing the agent-focussed client to orient itself accordingly as LTR or RTL. - Extended the web chat API to include asynchronous messaging.- Created a secondary, non-customer-focussed web chat client for testing the asynchronous messaging and web chat APIs. Unlike the official client, this was deployed within Oceana as a quick way to test the API without customising clients.- Creating a sample Sprint Boot application that used an encrypted JDBC connection to Intersystems Caché to investigate the effects of porting Avaya Oceana to a microservices-based architecture.

I moved onto the Avaya Oceana contact centre solution a few months into 2016. My primary contributions here were:- the reference customer-facing client for our webchat interface, allowing webchat to be tested and demoed to potential customers. This client was ported from the previous one for AACC 7, and written in vanilla JavaScript and Bootstrap. It had to be integrated with numerous other APIs, customised for specific customers at irregular intervals and manually built every sprint for at least 2 1/2 years until it was finally integrated into an official build.- JDBC encryption for the InterSystems Caché database used by the webchat components. This required me to work around a platform incompatibility between that database, our platform and the Apache Commons library.- The user interface/dashboard for a Spring-based visualisation tool for the Caché database. During a productisation drive to turn it from an internal debugging tool into an official product, my internal wiki page on how to use it became the official user manual.- Refactoring and cleaning up a JavaScript SDK for the agent-facing Oceana client after the previous maintainer left. The SDK had no existing documentation and had to manually built each sprint for a year until it was finally integrated into an official build.

When starting out at Avaya, I worked on AACC 7. My primary task was porting a legacy webchat client from using long-polling inside PHP to using WebSockets in JavaScript. I also had to write a new backend endpoint to accept a JSON request to schedule an outbound telephone call, replacing a legacy SOAP interface.

While studying for my Master's degree, I supervised labs for a course in Internet programming. This involved helping other students learn the basics of HTML, JavaScript and CSS.

As a side job while studing for my Master's degree, I helped to supervise labs in a database course. For this, I had to help students write SQL queries to create tables or find particular pieces of data, as well as showing them how to create reports and forms in Microsoft Access.