A legacy controller, moving to Go with one engineer and agents
An agricultural equipment maker ran its control services in Python, on ARM devices built with the Yocto Project. One of our engineers is moving them to Go with agents. The new code runs next to the old fleet during the change.
The engineer answered the design questions and decided what the agents built. The agents wrote the code, the tests and the reviews.
- 171 h
- of tracked engineer time
- 20 of 26
- services already run in one Go process
- 547
- merged pull requests, and not one revert
- 34%
- of the pull requests came from unattended agents
The port is still in progress. The test code is larger than the product code: 60,107 lines against 43,666. The 171 hours do not include 16 hours of machine time for CI, tools and unattended runs. On i.MX7 boards, the one Go process uses 91 MiB of memory, and the 20 Python processes used 481 MiB. The boards run different product configurations, so this is an observation and not a controlled comparison.
Read the case





