We are currently thinking about how to break that barrier.
When talking about configuring Avo, it's not really about having the best ruby developer. Instead, you just need a crafty developer.
If you bring in any PHP/JS/Python/INSERT_PROGRAMMING_LANG_HERE developer, they will know how to write that one-liner that adds that new field to a resource.
The alternatives are to use "general purpose" low-code tools (like re-tool) or mash it all together yourself using packages like AG Grid, both having the burden of a steep learning curve and continuous maintenance. With Avo, you need to know a bit of ruby and let it help you get the job done.
Avo is designed to be a bit boring like Rails. You build it; it works, and then you forget about it.
When talking about configuring Avo, it's not really about having the best ruby developer. Instead, you just need a crafty developer.
If you bring in any PHP/JS/Python/INSERT_PROGRAMMING_LANG_HERE developer, they will know how to write that one-liner that adds that new field to a resource.
The alternatives are to use "general purpose" low-code tools (like re-tool) or mash it all together yourself using packages like AG Grid, both having the burden of a steep learning curve and continuous maintenance. With Avo, you need to know a bit of ruby and let it help you get the job done.
Avo is designed to be a bit boring like Rails. You build it; it works, and then you forget about it.