Cantor’s expertise is based first and foremost on the engineers.
Each of us exerts in turn the three facets of software engineering, whether in customer operations or for our internal R & D. This is what allows us to leverage best practices and feedbacks.
It is a state of mind: spare the source code! The more source code there is, the harder it is to maintain and develop: we do not like bugs, neither for our customers nor for us. So we use a maximum of libraries and objects designs by retaining the most appropriate technologies. For the customer, it is also less development man.days and therefore more responsive support.
It is also to use advanced tools and development techniques or to maximize the technology capabilities of proven products without “tinkering”. […]
Anticipation is the key. Anticipate technical issues, of course, but also the needs of users and of the customer: we often operate in situations where needs and business rules are not formalized. Whether the subject is complex or innovative, it necessarily makes it delicate for the customer to formalize.
We incorporate into our designs stability and functional scalability so that technology be at the service for users needs and not the reverse. From this point of view, the practice of open source allows us to quickly identify what can be reused and what can not. […]
It is to find the “right” solution to integrate the customer’s application into his information system. We do not see software architecture as a set of software interfaces: it is necessary to think of it, of course, but we must also think about the use of the information system dynamics, about data life cycle, about processes.
It is necessary that the software architecture and the functional architecture be compatible and consistent with the big picture. Sometimes, of course, we are forced to compromise: but it must be mastered and anticipated. […]