In addition, Ruby on Rails is very database driven. To start, you do not need to know the features and scope of all modern databases - but experience with one relational database is needed. Better if it is PostgreSQL, but in fact, absolutely any relational database will do.

Now web developers are divided into specializations. Someone is well versed in the backend part: Ruby on Rails, databases, the Ruby language. Someone specializes in the frontend part: the visual presentation of the site using the JavaScript language, its frameworks, CSS cascading style sheets, HTML markup language. If your goal is to create a site alone, then to some extent you will have to master at least the basics of the profession of a frontend developer.

Learning the Ruby programming language requires almost nothing other than computer skills and arithmetic, but developing websites using Ruby on Rails will require a little more specific knowledge.

First, you will need to be familiar with the Git version control system. In my opinion, the technology is not the easiest for beginners, but without it it will not work to start working.

Secondly, the Ruby language is cross-platform and can be learned on any operating system. However, Ruby on Rails - more precisely, the ecosystem of components (gems) for it, is highly dependent on the operating system. For normal high-speed work on Ruby on Rails and delivery of the results of work to the server, you will need to know the basics of the Linux operating system. And in real work, a Ruby specialist will most likely be waiting for Linux or MacOS.

Project management systems / task managers

Ruby on Rails was originally designed to implement a project management system Basecamp. Also,

Redmine (a popular and free project management system) was created on RoR. Therefore, when working

on Rails projects, the use of such systems is “voluntary-compulsory”. All systems are integrated with

version control systems, which allows more flexible control of project development processes.

There are no Ruby on Rails developers

To begin with, there are developers, but they are less numerous than PHP developers. This is due to the

different entry threshold into the development of technology (usually people get into Ruby after several

years of PHP), which indicates the quality of developers. Good developers are equally scarce in all

technologies.

Ruby on Rails developers are very expensive

High-level developers are really expensive. Moreover, they are equally expensive in any programming

languages ​​and platforms. There are few cheap developers in RoR due to the lack of bad developers

in the community (not without exceptions, of course).

Deploy

The Ruby on Rails environment has many handy and nice tools. Including the tools that are used in

the deployment process. For example, using Capistrano, rolling out a new version of the application

to the production server (or several servers) will require one command in the console: cap deploy.

Version control systems

When developing any Ruby on Rails project, the use of well-known version control systems is implied.

The use of git is, as they say, "voluntarily-forced", since many systems for automatically deploying a

project to "combat" servers do not work without them. RoR programmers initially, when learning the

platform, are forced to master git, since numerous code examples in the documentation imply the use

of these version control systems. Largely because of this, it is easier for inexperienced beginners to

start learning PHP and not touch Rails until they reach a certain level of understanding of web

development as such and its principles.