Schedules ETL

back arrowBack to projects

Description

During my time as a developer for Universidad de las Américas (still studying but got hired full-time after my intership). We had an ETL process that would generate teacher's schedules daily running solely on the database that was taking too long (6+ hours) so we decided to migrate it to a background service that would run nightly (we had windows servers at the time, so we opted for a C# program). Ended up doing the development by myself and got the run time down to about 15minutes.

Challenges

  • There was no testing culture in place, so I did not write any tests and got a couple of (preventable) issues when we first deployed it.

Lessons

  • Learned the importance of unit tests specially while migrating existing functionality to a new language.
  • This was my first job, so I learned how to work with a team and take ownership for my mistakes.