Build
Reverse-engineering a 128-class banking SDK
An undocumented vendor SDK blocked the whole mobile team, so I read it.
- Problem
- A 128-class Kony and Temenos banking SDK shipped without the documentation the team needed to integrate it, and work stalled.
- Decision
- Reverse-engineered the SDK class by class until its behavior was understood well enough to build on.
- Result
- Unblocked the entire mobile team.
- Kony
- Temenos
- Mobile
- Reverse engineering
Vendor SDKs in banking often arrive as compiled artifacts with thin docs. One of them, 128 classes deep, sat between the team and a release. Rather than wait on the vendor, I worked through it class by class, mapping behavior until the integration path was clear.
It is the kind of work that never shows up in a feature list, but it is the difference between a team that is blocked and a team that ships.