Introduction
Levatas undertook the task of redesigning Leap’s legacy desktop-based financial tools, aiming to create a web-based application that not only retained all existing features but also introduced new functionalities and enhanced client management features. Central to Leap’s business is The Leap Model®, a collaborative framework for financial advisors and their clients to oversee the entirety of the client’s financial landscape. The model comprises 27 drawers, each representing various types of financial assets.
Key Features
- Custom financial calculators
- Hybrid financial presentations with embedded calculators
- Comprehensive client relationship management
- Add/Edit/Remove customer relationship
- Inbox messaging
- Sharing financial calculator scenarios
- Hypothetical wealth changes and projections
- Subscription tier options
Technology Stack
| Category | Technology |
|---|---|
| User Interface Framework | Knockout.js, jQuery |
| Language | JavaScript |
| Styles | Sass |
| Routing | Sammy |
| HTTP | jQuery.ajax |
| Testing | Jasmine |
| Deployments | Google Cloud |
| Authentication | Java / Spring Backend |
My Role
Introduction to Project
Leap marked my first major coding endeavor. Initially serving as a quality assurance analyst and junior developer, my role transitioned towards full-time development. This dual perspective afforded me unique insights into crafting comprehensive test plans and understanding the project’s logical flow.
Development Journey
Gradually acclimating to the codebase, I initially tackled minor tasks and bugs to familiarize myself with frameworks such as Knockout.js and jQuery. As my proficiency grew, I undertook the implementation of complete features.
Notable Contribution: First Feature Implementation
One of my initial projects involved developing a hybrid presentation and calculator tool. This innovative feature combined narrative-driven presentations with interactive financial calculators, empowering advisors to engage clients effectively.
Development Methodologies
Leveraging tools like Google Sheets for planning and Test-Driven Development (TDD) with Jasmine for implementation, I ensured code robustness and accuracy while optimizing testing strategies.
Lessons Learned
- Code Consistency: Adhering to established coding conventions minimizes maintenance overhead.
- Solution Planning: Preliminary solution planning aids in identifying and rectifying errors early in the development process.
- Testing Best Practices: Focus on testing overall functionality rather than implementation details to streamline maintenance.
- Effective Estimation: Through experience in Agile Scrum, I refined my ability to gauge feature complexity and break down tasks into manageable increments.