## Background
## The Problem
## The Solution
- Validating the existing code on two hardware configurations: the old and the new one.
- Adjusting the code to the new PCB and creating PoC.
- Pruning unnecessary abstraction levels, enabling easier development setup and CI pipeline usage.
- Defining processes for testing, code-building, new software releases, and provisioning.
- Creating a long-lasting solution for automated testing.
## The Process
We cooperated in a small team: the Client’s CTO, their junior software engineer, and our software engineer.
The workflow was organized fully remotely. Each point of contact had its own device set. Meetings were handled using long-range communication.
The final decisions were up to the Client’s CTO.
## The Effect
- Reduced Maintenance: fewer on-site battery changes mean lower travel costs for the end client.
- Enhanced Efficiency: handling only one battery saves time.
- Sustainability: halving battery waste supports a greener future, which is one of Traplinked’s principles.
## JERRY3 Project Resources
Recommendations
About the JERRY3 project
## Project Background
The industry, as well as regular households, are looking for modern ways to control the pest population. The solution ought to be efficient, low-cost, and easy to use. Moreover, it should not harm captured animals and ensure their well-being.
Abiding by these principles, Traplinked created an innovative pest-capturing device incorporating sensors and IoT solutions.
## The Team
The project was handled by a 1-person army – Maciek. With extensive knowledge and the ability to solve complex problems, he was the best pick for the job.
## The Result
The biggest value Maciek delivered to the Client was meeting their needs within time and budget. Therefore, Traplinked met their goals associated with the JERRY3 project.