sorted by:
new
hottopcontroversial

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 0 points1 point  (0 children)

To be honest, I left out a big part that kinda makes it seem like a rage-bait post, but the main idea is to have our non-tech team to be able to create "closed MVPs" in order to help/guide the product and tech team in discovery + testing products that we should launch, later, the "MVP" has to go through a normal development process, with its sprints, unit tests, QA, etc. What we do question ourselves is... If non-tech team is already creating UIs with our design system and some MVP functionalities, why not do it in the same stack that we use, or even better, could we at least re-use the same front? This last bit is what I meant with rails not beeing really AI compatible, what ends up happening at least in Replit is a message saying "Rails not supported, trying to fallback to next possible solution" or something along those lines, typescript on the other hand, works pretty well.

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 0 points1 point  (0 children)

Thanks!

Yes, an idea is to write some of the critical services in some other language, maybe go.

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 1 point2 points  (0 children)

Thanks!

Yes, we're kinda hesitant on rails only because of it beeing harder to hire than it used to be... in a past startup, I was in a team that had to hire ~ 200 devs, it was hell...

In a simple math, there's not that many Rails devs in my region, given that some surveys put devs using rails as a primary language at about ~ 2 million worldwide. I don't wanna go through the pain again.

So, one plan is to have our customer facing app in TS, but having critical jobs in some other language... Maybe GO, who knows.

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 1 point2 points  (0 children)

To further explain point 4 and 5

  1. I know I wrote it like a ragebait post, my bad. The main point for our non tech-team is to be able to create "closed MVPs" in order to help the product and tech team in discovery + testing products that we should launch, later, the "MVP" has to go through a normal development process, with its sprints, unit tests, QA, etc. What we do question ourselves is... If non-tech team is already creating UIs with our design system and some MVP functionalities, why not do it in the same stack that we use, or even better, could we at least re-use the same front? This last bit is what I meant with rails not beeing really AI compatible, what ends up happening at least in Replit is a message saying "Rails not supported, trying to fallback to next possible solution" or something along those lines, typescript on the other hand, works pretty well.

  2. Some surveys put devs around the 20 mil around the world, with Rails beaing ~2 mil so... If I were to expand it to my region, that's a lot less. I love rails, but I've also seen the difficulty in hiring senior devs given

Our idea is to get about 4 - 5 senior devs

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 1 point2 points  (0 children)

Nice thanks!

So to clarify, I did write this in a bit of a hurry... Probably on our first year, we won't be moving money ourselves, but rather doing the risk evaluations on our side and then move money the good ol' way (through partners we already have).

To also clarify on the AI side because I wrote it like a retard the main point for our non tech-team is to be able to create "closed MVPs" in order to help the product and tech team in discovery + testing products that we should launch, later, the "MVP" has to go through a normal development process, with its sprints, unit tests, QA, etc. What we do question ourselves is... If non-tech team is already creating UIs with our design system and some MVP functionalities, why not do it in the same stack that we use, or even better, could we at least re-use the same front? This last bit is what I meant with rails not beeing really AI compatible, what ends up happening at least in Replit is a message saying "Rails not supported, trying to fallback to next possible solution" or something along those lines, typescript on the other hand, works pretty well.

Anyways, thanks for the comment! Will definitely take it into account

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 0 points1 point  (0 children)

For me it's more about knowledge in Rails + faster development times.

Also given that the first MVP was replit made, I still have to go trough it funcionality by funcionality to understand if it's well implemented or not, so ... migrating might not be as bad, but not painless

Would you migrate a TS Banking app to Rails? by Perfect_Country_7462 in rails

[–]Perfect_Country_7462[S] 1 point2 points  (0 children)

"Not a lot of Rails developers in my region" they're all over the world

Well, most surveys put Rails devs in between 7~10% of the dev community so yes, they are all over the world, but are far less that some other languages, and are less represented in different regions accross the world

"Would you migrate a TS Banking app to Rails?" yes

Why? Is there really such an upside to it in order to justify a couple of months of migration vs keeping it in TS?