My first ‘big’ ruby project

It has been a year since I started my “big” ruby project.

The purpose of it was to build an e-commerce site where users could select product model and then select quantities of particular products (color and size).

I made 4 revisions. I had number of ‘A-ha!’ and “O.M.G. this way is so much easier and leaner’ moments. Every month for the past twelve of them I placed this project as my goal to finish. And I worked hard at it, but it is still far from functioning and showing the code that I feel pround of.

That being said this blogpost will be a eulogy for this project. I will leave it on my github account as a reference of ‘self-learning’ and perseverance, but it is time to move on to new things.

What I learned

  • Being super clear on client, design and development requirements.
  • Finding modules and breaking them down into a separate components, until one doesn’t work flawlessly and until you don’t have tests for particular feature don’t even move on to the next step.
  • Setting up environments and being confident in how to manage it.
  • Understanding the workflow you are going to engage — working with other developers, demoing to clients, deploying to production, refactoring, adding improvements.

What I am pretty happy I got figured out

I understand how for others certain pieces seems like a no brainer, but I was genuinely very happy when I got following items working for me:

  • Rails project & Heroku integration
  • CarrierWave Uploader for images
  • Localization for the site
  • I learned how to use JavaScript in the project
  • Utilize partials, helpers and .map function
  • Mailing system automation

What still needs improvement

  • Design style consistency 
    I was toying around with different looks for the site so every form looks slightly different then other. One view looks different then the next. Plus my rails knowledge sometimes hit the dead-end and my intention to deliver on good user experience had to be compromised.
  • User experience
    There is still pretty unpredictable where you will find submit button and how it will behave (returns you to the same page, or directs to the list of pages, or to the object page);
  • System messaging 
    It is very scattered through the site sometimes announcing about saved changes, sometimes skipping that step all together.
  • Refactoring to DYI principle and ruby, javascript style guides

For now

To view the repository visit:

Like what you read? Give UloDev a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.