Chapter Mobile
Welcome to LUCE
What do we do at Luce? We solve value challenges by using technology and data to accelerate digital transformation in society.
We are very good at what we do, we have integrity, we are close, and our projects are the most powerful and innovative. This is how our clients describe us. We believe that technology and data can “change the world”.
At Luce IT every person matters, every person participates, and what we will be in the future is built TODAY by all of us.
We are a great team!
How we are doing and our goals.
In themobility teamwedevelop and maintainmultiple apps in different technologies.
The development of a project consists of different parts:
Source code. Following a software architecture pattern, good programming practices and complying with quality controls.
Version control. Following a branching, versioning and naming structure for easy tracking.
Testing. They will ensure the quality of our artefact and help us with the fear of breaking things when they are changed.
Deployment. Distribution of the device to the customer with certain quality guarantees.
Documentation. This is essential to ensure the maintainability of the project and to make life easier for new colleagues entering the project, or for ourselves if we are away from the project for a long time.
Currently our projects do not follow the same programming practices, nor the same version control structure, we do not do testing and the documentation is scarce, non-existent or badly structured. For this reason we have set the followingobjectives :
Source code: to unify and improve the way of programming of each member of the chapter. Our code will go through static quality analysis.
Version control: follow all the same way of working in GIT, this point is more advanced, but we are still forgetting some details.
Testing: given an established software architecture pattern, start introducing tested functionalities little by little.
Deployment: automate deployments by orchestrating them with the CI/CD tool (currently Jenkins).
Documentation: pte. defined by chapter lead.
