FastRuby.io is a specialized Rails upgrade service. We have worked alongside teams from 1 to 100 people, upgrading applications without interrupting product development. Whether you’re stuck on 2.3 or want to prepare for 7.1, we’ve seen it all before and know the best approaches. We’ve fixed thousands of old dependencies and evaluated countless migrations Our years of upgrade experience means you can hand over the work to us, freeing up your developers to concentrate on shipping new features. Need to accelerate your Ruby application? Check out our Tune Report and invest in a comprehensive long-term performance plan.
FastRuby.io | Ruby Upgrade & Performance Services的外部链接
520 Carpenter Ln
US，Pennsylvania，Philadelphia，19119
If you are around Buenos Aires today, don't miss the Ruby Sur meetup! #Ruby #BuenosAires
Buenas! Se viene la primera meetup de este a?o en Buenos Aires ???? Serán dos charlas. ?? Báez 265, oficina de Roxom (Las Ca?itas, CABA) ? Pueden anotarse en la página de Meetup. También hay un link de YouTube para los que no pueden ir presencialmente. Los esperamos! https://lnkd.in/dJD3RphQ
Changing an engineering culture takes time. It takes time to get every engineer in the company to buy into new best practices, boring processes, and battle-tested systems. You can certainly do it, but it won't be a thing that changes from one month to the other. When we launched Bonsai, we believed in this concept: You can consistently pay off technical debt a little bit every month. On month one you can start by addressing security issues. You can implement processes that quickly detect new vulnerabilities being introduced into your dependencies and codebase. On month two you can upgrade your Rails defaults to use the version you're currently deploying to production. On month three you can discuss what's an acceptable level of complexity in every file of your application. And so on... Check out our slow & steady approach to technical debt remediation in the latest article by our CTO (Ernesto Tagwerker) #TechnicalDebt #BestPractices #CodeQuality
?? Slow and steady wins the race (Even in business development, content marketing, and technical debt remediation) In this day and age where everything needs to happen now and we are constantly looking for silver bullets to kill fantastic beasts, I'm here to tell you that it's okay to slow down. There are countless examples of this problem and I'm here to share 3 different scenarios that I see every day: * Business Development * Content Marketing * Technical Debt Consistency is key. Let's explore that in 3 different examples.
We are really excited about this update! ?? RailsBump.org is now maintained and supported by our #OpenSource Team.
Today I'm happy to share that RailsBump.org is now maintained and supported by the #OpenSource Team at OmbuLabs! ?? RailsBump.org is a valuable tool to check compatibility between your Gemfile.lock (or a #Ruby gem) and modern versions of #RubyOnRails. This tool is essential for identifying potential roadblocks when preparing for or working on a #Rails upgrade project. On behalf of the FastRuby.io | Ruby Upgrade & Performance Services team, I want to extend our gratitude to Manuel Meurer for his dedicated stewardship of the project. The more I learn about the intricacies of this tool, the more I admire the passion and effort that went into solving such a complex problem. Thank you so much, Manuel! We’re excited to support and maintain this project going forward. If you have ideas, feedback, or suggestions, please open a new issue on #GitHub: https://lnkd.in/en9_FWk7 If you want to give it a try, submit your favorite gem or your application's Gemfile.lock over here: - Gemfile.lock feature: https://lnkd.in/eZtfDdka - gem compatibility feature: https://lnkd.in/eaRZbjtV https://lnkd.in/ehmsBjeb #TechDebt #Dependencies #UpgradeRails
What’s the cost of not testing your upgrade changes?
What's the cost of not testing your upgrade changes before shipping them to production? It could cost $500M or more... ?? At least that's what it cost Delta Air Lines and many others affected by the #CrowdStrike update. That's why at FastRuby.io | Ruby Upgrade & Performance Services and UpgradeJS.com | JavaScript Upgrade Services we take #testing so seriously. As a consultancy, it is not cost-effective to understand our clients' business before we start working on a #Rails, #Ruby, or #Node upgrade project. We rely heavily on our clients' test suite. If the test suite passes with #Node18 and it passes with #Node20, then that's a strong signal that our efforts on their Node upgrade project will not cause problems in production. In #RubyOnRails upgrade projects, you can check the code coverage percentage to give you an idea of how much of the application's codebase is exercised by automated tests: https://lnkd.in/g_a_u782 Testing is key. If you don't have automated tests, you will have to manually #QA everything before you ship changes to production. The best time to write an automated test was 10 years ago (when you started the application), the second best time is now... So, if you don't have automated tests, when is the best time to start writing tests? Today!