How I solve Business Problems using Rails

Understand the problem

The first step on the journey is to fully understand the problem you are trying to solve, know the how a process in being done and the Why, who determined the business rules, why it was determined, better understanding will allow us to craft better solutions and decide which trade-off we should take.

Once I do understand the problem I do prefer to write first the MVP, so we can start generating value, while getting feedback to keep enhancing the product.

is Rails the best tool?

But Why Rails? Rails follows a philosophy called convention over configuration, which in short terms means that you don’t have to think on how to structure your projects, which names you should use for your files, or wich libraries you should use to connect the DB to your application. more time working on bussness problesm, lest time configuring boring stuff. This is very important when you are working on Very fast paced places like startups, or with customers that requires speed on delivery.

When I do not use rails? When the product is the Front-end itself, and the UX/UI might manage complex states, then I would probably opt for another tool as React (and still use Rails for Back-end). I mostly don’t focus on having a unique original style, but instead on having a fast created using re-used components ux so we can focus on business rules and solving business problems.

Some use cases

For Building APIs

Rails is a Full-Stack framworkd, but you can initialize a project on API mode. even if you only shoose Api mode or you install alll gems, modeling relations, and bulding, and migrating the DB is way easier with the Rails ORM (ActiveRecord). You can have Simple API in a matter of a few hours.

For Building Dashboards

You can Write Server Side applications, but Event if you do need to build a dashboard, you can use the Rails asset pipe line and pin JS moodules using propshat, you can use Chart.js to implement charts.

You can retrive datat scheudling Back Ground Jobs, or you can implement webhooks to fetch data to proces and display.

To perform Integrations

Rails is so easy to read that writing integrations feels amazing. performance is enough to start and mange your first request. if you do have the change to growth there is enough room for optimization.

Again, we do have the Active Job + Solid Que combination super useful to trigger actions.

AI Assistance

Rails requires less lines of code to write an read, so it might be more token efficient to write Projects on rails.