3 ms·
> The idea is to do for ML development what Rails and Heroku did for web development. I think this is a great way to explain what you're doing. I'm working in
by edublancas 4y ago
> The idea is to do for ML development what Rails and Heroku did for web development.
I think this is a great way to explain what you're doing. I'm working in the same space (ML/DS tooling) and I feel like we, as the ML/DS community, haven't cracked exactly how Rails for data looks like, I actually wrote some ideas on this a while ago (https://ploomber.io/blog/rails4ml/ https://ploomber.io/blog/rails4ml/).
Congrats on the launch and best of luck with the product!
- neutralino1 4y agoThanks! I was a pretty heavy user of Rails in past jobs. They have a nice mix of good abstractions (Model/View/Controller), tooling (CLI, local web server), and best practices (how to name tables, fields, lifecycle timestamps, etc.). We think that is a good way to go: solid abstractions that experts can build on top of, but also more junior folks can get started quickly by following best practices. Ploomber looks great too, I like the breakdown of your SaaS offering.