All geek questions in one place

Ruby on Rails Project Launch Process

I am about to start a Ruby on Rails project, and I would like to hear how others go through the process of starting the application design . I have a lot of experience with RoR, but I don’t have many beginners from scratch with only vision impressions and I would appreciate the wisdom of others who were there.

I look for the order of events, the reasons for the order, and possibly why each part is important . I might think of a few starting points, but I'm not sure where to start.

  • Model design and relationships (entities, their relationships and their attributes)
  • Think about custom use cases (or storyboards) and implement a minimum to achieve this.
  • Create unit model tests, then create the necessary migrations and AR models to pass the tests.
  • Pull out the most basic version of the simplest part of your application and from there
  • Start with a template for the rails application (e.g. http://github.com/thoughtbot/suspenders )
  • Drill gruntwork first (User auth, session management, ...)
  • ...
+4
source share
1 answer

I found that for most projects the following tasks are performed:

  • Collect user requirements
  • Model Database Design
  • Building views
  • Layout Optimization
  • Find and explore plugins / gems
  • Testing
  • User Review / Acceptance
  • Expand Application
  • Documentation

After these years of working as a freelancer, I think that steps 1 and 2 are the most important (at least for small projects). Before writing any code, I urge users to first refine the entire user interface. The HTML skeleton is better than a written document. Users do not understand and do not understand the specifications of the software. They can only give feedback after they see that they can click something. So fluency in an HTML site is a useful skill. Sometimes I delegate a task to a partner as an SA role.

Rails is very good for building an ever-evolving scheme. Try using migrations and data fetching instead of writing SQL statements directly. I believe that I rely more on ActiveRecord overtime. script/console is a good tool to test this many-to-many relationship and build :conditions => .

Recently, I worked on several legacy databases, the establish_connection and set_table_name in ActiveRecord elegantly stuck the old and new databases.

I would also like to take this opportunity to thank Ryan Bates , I learn a lot of Rails from his railscasts .

+2
source

Source: https://habr.com/ru/post/1311034/

More articles:


All Articles