![rack app error handling request { get css js rack app error handling request { get css js](https://i.stack.imgur.com/Yt0LT.png)
It lowers the barrier to entry, but it also narrows the range of knowledge. It is no secret that most Ruby web developers are introduced to Ruby via Rails. Why not “Ruby On Rails” and not “The Right Way”? If I do not mention a particular topic, that means I am not aware of any specific issues with it. Clear steps like installing Ruby (via rbenv or rvm), managing dependencies via Bundler, etc., are not described due to the wide coverage of these topics in other tutorials. My goal is simply to make suggestions based on my experience.
![rack app error handling request { get css js rack app error handling request { get css js](https://miro.medium.com/max/1400/1*WX2qrsbYLMJ6HTAEdudjYQ.png)
They do not represent absolute truth or generally-accepted best practices. Important notice: All suggestions in this guide are my personal opinion. It is up to you, the reader, to decide whether you would like to use them or not. Sometimes I will suggest tools or gems (with comparison if possible), but these are merely suggestions to get you started. The format and advice is inspired by “PHP The Right Way”. This guide contains sections dedicated to very important aspects of web development, explanation (if needed), and lists of tutorial links. This guide is born from the question: “could you write a list of all the things that a good Ruby on Rails developer should know?” I decided to expand it to the whole of Ruby web development, and related “full stack” skills, but also limit it to the web, as it is not about Ruby in general.
![rack app error handling request { get css js rack app error handling request { get css js](https://womanforhireinc.com/images/128560.png)
Why not “Ruby On Rails” and not “The Right Way”?.