RS2I
Designed the frontend architecture and set the team's technical standards in an Agile environment.
- Company
- RS2I
- Role
- Frontend Developer
- Domains
- Enterprise software
- Stack
- Angular
- TIBCO BPM
- Bonita
- Software Architecture
The problem
RS2i installs BPM engines for its clients. The interface that shipped with those engines was dated and unattractive, so the company wanted its own frontend, sold as a package alongside the installation service. It had to work whichever engine the client ran: TIBCO or Bonita.
The approach
It was my first job, in a team of three developers, all junior. Without the title, I took on part of the lead role: I researched good practices and brought them to the team, which is where our coding conventions came from. With no senior developer to review our work, keeping the code quality high was the hardest part, and those conventions were our way of holding it.
I designed the frontend architecture in Angular to be independent of the engine, so the same interface could drive TIBCO or Bonita. We worked in Scrum.
The outcome
A single Angular frontend worked with both TIBCO and Bonita, without changes from one engine to the other.
Key achievements
01 //
Architecture
Designed the frontend architecture for an agnostic application capable of seamlessly interfacing with multiple backend BPM engines.
02 //
Standardization
Established rigid coding conventions and development best practices to ensure long-term code maintainability across the team.
03 //
Methodology
Worked in Agile (Scrum) development cycles.