Engineers keep working the same way, even after you tell them the old way is over, because that’s the workflow they know and trust.

Getting them onto the new one takes a transition period, documentation, repeated training sessions, and one-on-one conversations to answer questions.

In this piece, I summarize what worked for me.

Comments URL: https://news.ycombinator.com/item?id=49538342

Points: 1

# Comments: 1

The requirements:

1. Compliance: prove what is running where, to a customer's security team or a regulator 2. Speed: ship a fix to the whole fleet the day you have it, not the month you have it 3. Security: know which keys open which robot, and sign what you install 4. Control: stop a rollout, roll one back, and know the state of every machine 5. Visibility: know a robot is degrading before the customer phones you about it

Most of the conversation in robotics sits around hardware and AI and less is about how to ship and maintain them.

Some companies I talked to in the past are still using Founders' time bash scripts or ansible to deploy their robots. It's 2026, we must do better.

This is the intro, it looks at why updating machines by hand gets harder as a fleet grows and explaining what are the requirements.

Very much a work in progress. I'd be glad to hear from anyone who's been through it.

Comments URL: https://news.ycombinator.com/item?id=49255188

Points: 2

# Comments: 1

So, I am humbly sharing my thoughts on how to evaluate AI-assisted code without getting distracted by whether AI was involved. It’s also the first post on my new blog.

Feedback is very welcome.

Comments URL: https://news.ycombinator.com/item?id=49193731

Points: 1

# Comments: 1

Other than this, most material are available for free, but I would agree no direct pointers.

You have the ros community available for help on answers.ros.org, the discourse for more general questions and finally some slack community like the nav2 managed by Steve Macenski, the main contributor.

The Construct is probably the closest you can get.

At Brisa Robotica, we develop the Windrose product line to boost productivity and increase safety in the Supply Chain. We provide all-in-one kits to automate machines and robots! They require no physical infrastructure change and no new software. Windrose connects to your preferred WMS, ERP and MES. All of it with unmatched deployment speed, unmatched ease of use even on complex tasks and built-in alerting and monitoring. With every Windrose vehicle, we provide KPIs through a dashboard and an API, with data collected and processed from the vehicles.

We design and develop for logistics, industry, mining and food industry.

We have a background in research in robotics, along with experience in software engineering in startup environment. Thiago and I (the 2 founders) have acquired experience working abroad, so we are quite an international company from the start. He lives in Recife, I'm in Hamburg until soon. Our projects with customers follow a simple pipeline of integration of new sensors and vehicles into our poroduct line, then we work with the customer to make it work. Once it's added in our library, it's simple to scale up.

We are working with different tech stacks: ROS (1&2), Flask (migrating to FastAPI), AWS, Python (2 & 3), virtualization tools (vm, docker), IaC (ansible).

It's a unique chance to work in a brazilian robotics company, there are not many, and using state of the art software, with a skilled engineering team with experience, develop innovative products in a thriving market.

We welcome every new teammate with a tailored onboarding process, we develop together a personal development plan. As we use many open source projects, we tend to submit PR to them and contribute once in a while. Finally, nothing better to know that some of our work improves safety in deadly environments!

Apply by email: job@brisa.tech (feel free to mention "HN")