Thank you for the feedback shared.
Though the coded approach is meant to handle the scenario when you need to identify a row by any cell content but interact with another cell on that row. It is not a straightforward scenario and this is why it should be handled that way.
But you could data drive it or any other iterating actions. Here is an overview
how tests could be bound to different types of data sources. Once there is a data source you could also bind input and verifications in code
or use the data to data drive an element's find expression - either using the UI
or in code as well
If you would need to interact with the same cell you locate on page you could use the element's find expression - edit it to rely on text content
and data drive it to perform the same action multiple iterations.
I hope the above information will be helpful to you as well!