Modularity in software design with ROS
I know there's no one-size-fits-all answer, so I am asking. what would be the best practice or idiomatic way.
As a software engineer I am always looking for create abstractions and separation of concerns. Which leads to designing classes or modules or whatever tools the language provides.
When working with ROS, is the best practice to start by considering making a modular component a node. Or would I just as likely write a python class or module?
You may have already read through the ethz ros best practices page - I think it gets into some of this.
Thanks, I had not seen that. Will give it a read.