DEV Community

Cover image for Rebuilding My Ruby On Rails Skills with No-AI
Newton Jillian
Newton Jillian

Posted on Edited on

Rebuilding My Ruby On Rails Skills with No-AI

Rebuilding My Ruby on Rails Skills: Building a Production-Level Application from Scratch

It's been approximately 2–3 years since I last worked seriously with Ruby on Rails.

I've spent much of my recent development time working with JavaScript, React, TypeScript, and other technologies. However, I've always wanted to return to Rails and challenge myself to build something substantial with it.

So, I'm starting a new journey.

Introducing BizFlow

BizFlow is a multi-tenant business management platform that I'm building with Ruby on Rails.

The idea is to create a platform where businesses can manage their daily operations, including:

  • Business and employee management.
  • Customer management.
  • Products and services.
  • Sales and orders.
  • Invoicing and payments.
  • Expense tracking.
  • Business analytics and reporting.

Eventually, I want to introduce integrations such as M-Pesa, background processing, notifications, and a public API that could power a mobile application.

This isn't intended to be another basic CRUD application. I want to approach it as a real software product, with proper architecture, security, testing, and scalability considerations.

My learning approach

One decision I've made is to avoid relying on AI to write the application's code.

I want to get back into the habit of reading documentation, researching problems, understanding errors, and figuring things out independently.

My primary resources will be:

  • Official Ruby and Rails documentation.
  • Google searches.
  • Stack Overflow.
  • GitHub repositories and issues.
  • Technical articles and engineering blogs.

I'll write the code myself, make mistakes, investigate them, and learn from the process.

What I'm planning to explore

I'll gradually work through:

  1. Ruby fundamentals and object-oriented programming.
  2. Rails MVC architecture and conventions.
  3. Active Record and relational database design.
  4. Authentication and authorization.
  5. Multi-tenancy and data isolation.
  6. Business logic and application architecture.
  7. Automated testing.
  8. Background jobs, caching, and performance.
  9. REST APIs and third-party integrations.
  10. Production deployment and maintenance.

I'll start small and introduce complexity as my understanding grows.

Building in public

I want to document this journey consistently.

I'll be sharing daily updates covering what I've built, what I've learned, technical challenges, bugs I've encountered, and decisions I've made along the way.

I don't expect everything to work perfectly. In fact, I think documenting the difficult parts will be just as valuable as sharing the successes.

If you're a Ruby or Rails developer, I'd appreciate your insights, recommendations, and lessons from your own experience.

Let's see how far I can take this.

Day 1 starts now.

Top comments (1)

Collapse
 
ibuildinpublic profile image
Ehsan •

Coming back to Rails by writing BizFlow without AI code is a real way to relearn the conventions. For multi-tenant data, are you going with a tenant_id on every table from day one, or separate schemas later?