Kiran Ramaswamy

The company's production website was written in ASP Classic and needed to be upgraded to ASP.NET to accommodate the growing list of requirements. The development team was tasked with migrating the code, as well as gathering feature requests from relevant stakeholders throughout the company.

I was put in charge of the project and led a team of three others (a graphic designer, another developer, and QA). My responsibilities included working with all of the other people in the company to make sure their feature requests were adequately implemented.

We successfully launched the new site after about a year of development. After the site launched, I was responsible for maintaining it and communicating new feature requests with our team.

The client was the call center of a financial institution in Canada. The call center was using an MS Access app to manage their interactions with clients. These interactions included but were ot limited to handling app/cancellation requests, managing address changes, and validating/invalidating fraudulent transactions.

In the past, they had attempted to redo the app in ASP.NET; it failed due to massive scope creep. Our team was brought in to revive the project and try again.

We successfully migrated several vital parts of the application to a new ASP.NET solution and positioned our product to be able to handle more migrations if necessary.

Our company was tasked with the creation of a management portal to handle various tasks required by student unions, including but not limited to management of timesheets, events, jobs, inventory, and membership.

We developed a .NET portal which was implemented using an Azure SQL Server Database and an Azure-hosted website. Later, we revisited the project with other clients and adapted it to fit their specific needs.

After several years of being used, we decided to launch a new version, reworked from the ground up with all of the lessons we learned from the previous version.

The client had a requirement to import large amounts of data from different sources, primarily composed of flat files. They had set up a process of gathering that data and using bulk import tools within SQL Server to handle the importing. However, the recordsets were often composed of tens of millions of records and the import process was taking days to complete.

We were tasked with developing a new method to import the data, along with the added requirement of also capturing any failed imports to diagnose, ideally without interrupting the primary import process.

We solved this problem by using SQL Server Integration Services (SSIS). We developed several pipelines to stream the data from the flat files to their destination tables. We were not only able to reduce the overall execution time from days to mere minutes, but also handle import problems by transferring those records to secondary error tables. Depending on the severity of the error, these could optionally have the primary record continue to import, with null or default values as required.

The overall solution was also easily extensible to different types of imports and became the primary method for importing data for the company.