Linx is the flagship product of Twenty57. It is a low-code, drag-and-drop development platform to build and host APIs, automation and integrations without the need for code, frameworks or infrastructure.Among my responsibilities are leading a team of 5 developers, fielding technical questions, design decisions, future direction and priority discussions with the director, splitting up work into smaller manageable pieces, releases (planning & execution) and resolving issues handed up by the helpdesk.

Stadium - a low code, drag-and-drop web application builder - is the sister product of Linx and used in many well-established financial institutions. ( https://stadium.software )Among my responsibilities are leading a team of 5 developers, fielding technical questions, design decisions, future direction and priority discussions with the director, splitting up of work into smaller manageable pieces, release planning and resolving issues handed up by the helpdesk.

I was assigned as the lead developer of a payments and collections processing system, called CentralPark. My responsibilities included any new development as well as the partial redesign of the current version of CentralPark.In Dec 2012, when I was moved on to a new huge project - the rewrite of Digiata's second flagship, and sister product of Linx, called Stadium. The main goal of this project was to take the current Stadium product - which required a lot of intimate and specialized knowledge to set up - and rewrite it so it would be able to be sold as an off-the-shelf product or a product that somebody outside of Digiata could use without the need or help of Digiata staff. I filled the role of lead developer of this rewrite up until September 2016 when I was promoted to product owner of Stadium.All product development later moved from Digiata to its parent company, Twenty57. When this happened Linx and Stadium became part of the Twenty57 company.

From lead developer I was promoted to Product Manager of CentralPark, a web application processing payments and collections. This position involved - Interfacing with clients - Decision making of where the future of CentralPark lies, as well as the direction it should head in - Architecture of new development - Managing the dev team (1- 2 developers)

Starting my career in Digiata, I developed a prototype of a mobile chat server/client in C# and Java ME for one of their clients. From there, I moved on to the development of "The Performance Engine", a program used to calculate and create reports of financial performance over a period of time. Next, I moved on to a team developing the flagship product of Digiata, called Linx. Linx is a development platform to build and host APIs, automation and integrations without the need for code, frameworks or infrastructure.

I formed part of the international delivery team in Postilion. They were involved in the development of additional software plug-ins and components for a home-grown financial transaction routing system built by Postilion. These plug-ins were tailored specifically to the specific bank or financial institution's needs. The development language used was Java. During my employment there I was sent to India twice, once to Greece and once to Indonesia for client implementations. In addition to this, I was sent to India for 3 weeks to act as a mentor for the newly employed employees there.I was also responsible for managing three resources in the international delivery team.

I was part of a two-man team who developed the website and web services for the Argus Cycling race. The system comprised of building web services to expose any common data, e.g. cyclist’s names, cyclist's medical details, of any cycling race held in South Africa to any interested party.In addition to the web services, a generic website was developed which could be customized and configured, without code changes, for an event. Skins were used to change the appearance of the website and a ‘Rule Engine’ determined the restrictions or compulsory information required for applications or entries to the race. The website was made available to any association/club that would like to use it for their races.The website and web services were developed using ASP.NET and C# respectively.

During my employment at AST, I was involved in several projects, where most had to do with the integration of the MS Project Server. For most of my employment at AST, I was working in close conjunction with or was contracted out to Microsoft SA as a technical resource. I was part of one of the, at that time, largest EPM implementations in South Africa. This project was led and managed by Microsoft SA.