3 ms·
I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magi
by t-writescode 5y ago
I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk.
Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.
- revskill 5y agoBecause the ease of installation of Ruby, RoR and deployment to Heroku. It's cross-platform. So u can bring your application to production in like 30 mins. In era 2010, .NET stack couldn't offer you that. I wrote about 4 production application in Ruby stack in 6 months, it's super productive and the Ruby language has OOP/FP done right in comparison of other languages, too.
- t-writescode 5y agoI worked in Microsoft shops for the majority of my early career, so cross-platform didn't matter to me. C# had task-based async and a very good, compared to the competition in Java, database framework to work with. Seriously, how doesn't Java have named parameters yet?
- jeremyjh 5y agoThe only reason this seems special to you is because its your story. Your story could have happened with a lot of different languages though.
- regularfry 5y agoOne part of the story that's probably relevant is that RoR makes getting started with relational databases easy. That can be extremely intimidating otherwise; I meet a lot of juniors who have never touched them and don't know where to start. Because it does cover the full stack, in a way that devs in a conventional enterprise wouldn't ordinarily do, and gives you pretty good hand-holding while you do it, it takes a lot of the fear out of parts that might otherwise look intimidatingly complex.