I am currently helping the developers for the regulatory section of the Tax Pro Software Blockworks learn best practices in coding and unit testing. I am helping them increase their skills in problem solving through programming. I am also learning their systems so I can also contribute to their enhancements for the 2015 tax season. I am becoming familiar with their internal utilities and architecture so I can better help the developers write and refactor their code so it becomes better maintainable and scalable for future enhancements. I’ve been working closely with the full time engineers and management to help refine their processes and to help find the most efficient way to increase the skills of the non-senior developers.

I have written an application that consumes (and creates/modifies) an XML file describing the properties and objects of a system and then outputs classes and other code segments for the system in C#, C++, and C for use by multiple departments to allow a consistent interface between software and hardware. I am in charge of maintaining and enhancing the backend COM applications and libraries for the Converge Pro, Interact, and Chat products. I introduced to the team WPF and the advantages of using it for the user interface. I have written the user interface and communication layer to the video card in the Collaborate All-in-one product (no longer shipping). I have written a virtual keyboard designed to run on a small USB touch monitor and control Microsoft Lync clients. I have written services to connect and interact with a custom audio card and custom IR card for the Collaborate Room and Room Pro video collaboration products. I have ported the COM interface for Converge Pro to C#, reducing the complexity and lines of code by almost 50%. I have written a simulator on Linux and Windows to communicate with the configuration applications currently under development to speed up the process of development as the hardware is being developed. I have been an integral part of the architecture, design, and implementation of the latest product line. I wrote a code generator that takes as input properties and device configurations and outputs C# and C++ code to configure and control the devices.

Using Agile and Scrum methodologies, I worked in a team to design and write plug-in libraries to control the audio equipment over Ethernet using Microsoft Visual Studio 2008 and C#. For one of the products, I wrote a graphical layout manager that organized a dynamic number of controls within a window so it would maintain a layout that audio technician professionals would be used to seeing. Testing and debugging of this software includes using WireShark for Ethernet traffic analysis and NUnit for writing automated white box regression tests. I worked closely with the Quality Assurance department so I could learn what they expected from the software and also to discuss some design issues that would help everyone do their jobs faster and easier.

I wrote the first revision of the REV System Software from scratch. The software included an API written in C so other applications, such as Iomega Backup, could easily interface and control the REV drives. Writing this software required the creation of readable documentation on how to use the API as well as writing utilities to modify REV’s UDF file system properties, write and read access protection for the REV disks, and to format the disk, to name a few. Before the REV System Software, I was in charge of maintaining and upgrading IomegaWare. I wrote an automated test tool that helped find a memory leak in the Windows 95 driver that caused the operating system to become unstable. I helped solve and fix defects in the drivers on Windows XP/2000.

The software solution I helped produce was a workflow system for the parts procurement section at Hill Air Force Base. I wrote the user interface and system architecture document for the system. For this document, I used UML to write the use cases that met all of the requirements for the system. I wrote the high level engineering document that addressed the architecture that would be used to satisfy the use cases. I wrote the detailed low level engineering document that described in great detail what exactly would be implemented in code for the system. Before this document, I maintained the data repository that the old workflow system created.