I currently have both development and architecture responsibilities for many of OpenText Exstream’s main products.One example of a major contribution I have made during this time is the development of the Exstream Empower editor. Empower is a web based word processor-like product which allows for complicated documents. This product is written in HTML, JS, Typescript and Angular. I developed the original prototype which proved out the technology and allowed us to verify that performance would be adequate. I developed the testing strategy which was comprised of using Jasmine for unit testing and Selenium Webdriver for functional, integration and E2E testing. Eventually a team of 20+ developers (including myself) were assigned to the project and I helped to onboard and direct new development until the product was released.I am also a member of Exstream’s Technical Architecture Group which is responsible for Exstream’s technology roadmap as well as reviewing/investigating complicated enhancements.

I developed a WYSIWYG designer that allowed users to design complicated user interfaces. These user interfaces could then be rendered as a web page, an Android app or an IOS app. The designer was written in Javascript using Enyo.js. It used Cordova to build the Android and IOS apps.

I led the development of the HP Relate editor which was a SaaS based document editor that allowed you to create simple quotes and proposals for small and medium sized businesses. The editor was written in ActionScript and deployed in Salesforce.com with some components in Amazon Web Services (AWS). I developed most of the editor code as well as the integration with Salesforce.com.

I was ultimately promoted to team lead of the UI team. Additional responsibilities included helping to onboard new employees, doing preliminary reviews of new enhancement requirements, and helping to manage defect queues and performing code reviews for other developers.One example of a major impact I had during this time involved dramatically improving the aesthetics of the UI. Microsoft had just released a feature pack for MFC which allowed an expanded set of modern looking UI components. I brought this to attention of product management who were very supportive. I used this feature pack to improve the appearance of all the UI components as well as worked to replace the majority of the icons. One of the major detractors sales was having with the product at the time was the aged look of the UI and this dramatically helped in that respect.

I developed C++ code on a large codebase with over 2 million lines of code. I worked primarily on the UI team which was responsible for development of three different MFC based Windows applications. Some of this work was simple dialog based UI development as well as more complicated work such as Exstream’s Live product which is a very complex version of a word processor. My responsibilities included fixing defects, helping support debug problems, as well as implementing new enhancements.One example of a project I was responsible for was to improve the GDI leaks present in the product suite. These leaks were problematic because they were only noticeable when you used the product for long periods of time (many hours) without closing the application. At that point you would get a crash with no indication of the problem. I modified Microsoft sample code that used DLL inject to allow you to execute code when certain Windows API functions were called. Using this technique I could determine when GDI objects were created but not destroyed. When the application would close it would dump a text file of all leaked objects and the call stack when the object was allocated. This project was completed over the course of about a month and resulted in a much more stable application.