I am Ademar Tutor.

Ruby on Rails

I have had the privilege of growing alongside Ruby on Rails, starting my journey with this technology in 2009. Each version of Rails has offered unique learning opportunities, and I'm grateful for the insights gained through these experiences.

Rails 2.3.5 (2009 - 2010): My initial experience with Rails was during my final college year. At that time, I was working on a CodeIgniter (php framework) library for my thesis that logs and creates a UML to help developers debug code issues. The moment I actually read through and worked on a production Rails app which was a game on Facebook, I realized my thesis would not be useful in production. 😅The logs of Rails was really intuitive.
Rails 3 (2010): This version was a really big leap for Rails because of the Merb team merge. A lot of things were introduced on Rails on this version. The main issue at that time was migrating 2.3.X apps had a lot of issues, including Gems no longer working.
Rails 4 (2013): Transitioning to Rails 4 was a smoother experience. In January/Feb that year there was a mass assignment issue with Rails (where we could do SQL injections). On Rails 4, they made strong paramaters a default.
Rails 5: Turbolinks 5 and Action Cable was introduced. I think this was Rails answer to SPAs and hybrid mobile apps. During this time, I learned Turbolinks 5 and used Turbolink-iOS adapter to build and launch an iOS app on the Appstore.
Rails 6: Although ActiveStorage was introduced in 5.2. The projects I've worked on started adoption ActiveStorage at version 6. This is mainly because when you used ActionText which was introduced at Rails 6, you see the advantage of ActiveStorage when images are easily embedded on the WYSIWYG.
Rails 7: On this release, Hotwire became the default front-end framework for Rails. Hotwire included tools like Turbo + Strada to make it easier for smaller teams to launch cross-platform apps.

Front-end Technologies

I have extensive experience in front-end development, particularly with React and similar technologies, spanning over a decade. Here's a breakdown of my journey.

2012: Began with BackboneJS, where I first delved into MVC architectures in front-end development.
2013: Transitioned to EmberJS, which I found to offer a more robust MVC framework compared to BackboneJS.
2015: Adopted AngularJS, facing challenges with code organization due to the lack of standardized practices at that time.
2016 - 2017: Shifted my focus to React/Redux, a significant leap in terms of code structure and organization. The official Redux documentation greatly aided in establishing a consistent code organization strategy.
2018 - 2020: Integrated StimulusJS into my projects.
2021 onwards: Embraced the Hotwire stack, continuing my journey with the latest in front-end technology.

Career Start

My professional software development career started in Cebu, Philippines in 2009-2010. My role was a backend developer working for a Ruby on Rails startup consulting company.

First Startup Experience

In 2011, I got invited by my friend to join a startup based in Cebu. The founder was a silicon valley-based entrepreneur who wanted to establish a company in the Philippines.

My role was as a full stack developer. The technology stack that Etroduce was built on is Ruby on Rails.

Starting my own company

In 2012, I started my company, Bootyard, a Ruby on Rails web development consulting company. Along with my cofounders, we grew the company and helped many startups with their product development.

Focusing on Codetoki

While doing consulting work, we also worked on our product startups on the side. One project that grew and had a lot of interest was Codetoki. We won multiple international accolades and were able to raise funding from JFDI.