Work Solutions for Progress / Communally
A .NET to Django port, bugs included
A deliberate one-to-one port of My Budget Coach, then a refactor into multi-tenancy for a national partner.
- Client
- Solutions for Progress / Communally
- Role
- Developer
- Period
- 2015 to 2016
- Focus
- Development, Migration
- 1:1 port fidelity, on purpose
- Multi-tenant refactor for AFCPE
- Team worked to a project lead
I worked on a developer team porting My Budget Coach from .NET to Django, partitioning the work with the developer project lead.
Why we ported the bugs too
The port was one-to-one, including the existing bugs. That sounds wrong and it is correct. Fixing behavior during a platform migration means that when something breaks afterward, you cannot tell whether the port or the fix caused it. Match the original exactly, confirm it, then change things deliberately.
Once the port was verified, I refactored the application to support a multi-tenant structure for AFCPE, a key partner, which is the change that let one deployment serve multiple organizations.
Screens
