Earlier quoted context omitted.
If a .NET developer who doesn't use proper source control seats next to you, then perhaps you should take a hard look at the place you work, maybe leave. When I worked with .NET I used TFS and Git. Also, I implemented RESTful web services using .NET's Web API, consumed by a large scale SPA implemented on AngularJS/TypeScript. I never had a complain. Now, I work on an open source stack, and Rails is suited to only one…
> Rails is suited to only one project out of the multiple web services and applications I deal with. What else do you use, and, if you don't mind elaborating, why did you pick those instead of Rails? My understanding is the more technologies you introduce, the more complex your infrastructure gets, so you're better off picking one web stack, one back-end, etc.
For the micro-services, Sinatra does the job very well, there is no need for all of the components that Rails provides; we like the flexibility.
Our front end developers have complete ownership of the two front-end apps, and they rolled with NodeJS because it allowed them to take advantage of their JavaScript skills.
The Rails app is an internal consumption app. It doesn't need to be fancy or have a need to scale. Rails and Bootstrap keep it simple stupid.
The meat of our stack is actually on the big data technologies we deal with, RedShift and Hive. We could honestly re-write any of the micro-services in .NET or any other stack for that matter, and still keep our infrastructure mostly the same.