Thanks for buying it and mentioning this.
You are right that the current checker is still too strict about matching my variable names and structure, and that is not where I want it to stay.
I am working on a Python validator that compares the parsed code as an AST instead of raw text, so you can use your own variable names and small structural changes as long as the logic is the same. I am aiming to have the first version of this in by the end of December.
After that I want two clear ways to practice. One mode tracks the editorial solution for people who want to drill that exact version, while still allowing harmless differences like different names and small adjustments in structure. The other mode treats your own code as the reference and lets the objectives and feedback adapt to the way you wrote the solution, instead of holding everyone to one fixed template.
If you have thoughts on what would make the checker feel natural and fair for you, feel free to share them here and I will keep them in mind as I make these changes.
I don't think this is a thing unfortunately. I can only think of the seasonal ROS Industrial trainings that are quite expensive.
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")
