<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Robot-Fleet on David Bensoussan</title><link>https://blog.bensoussan.de/tags/robot-fleet/</link><description>Recent content in Robot-Fleet on David Bensoussan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Aug 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.bensoussan.de/tags/robot-fleet/index.xml" rel="self" type="application/rss+xml"/><item><title>Updating Robots in the Field</title><link>https://blog.bensoussan.de/post/2026-08-11-updating-robots-in-the-field/</link><pubDate>Tue, 11 Aug 2026 10:00:00 +0200</pubDate><guid>https://blog.bensoussan.de/post/2026-08-11-updating-robots-in-the-field/</guid><description>&lt;p&gt;Ask a robotics company, especially a young one, how software gets onto a robot that&amp;rsquo;s already at a customer site, and the answer usually is someone driving there, accessing the robot, pulling the code and getting it to run, watching the robot move for a minute, then moving on to the next one.&lt;/p&gt;
&lt;p&gt;The reason is lack of awareness rather than carelessness. How many robotics companies have a DevOps engineer on the team? Most are led by roboticists and researchers who can make anything happen on a few robots. So a great deal of sophisticated software gets written, and then moved around manually.&lt;/p&gt;</description></item></channel></rss>