Optimization & Debugging Ruby on Rails Code
Budget: £20 – £250 GBP
As a Rails dev with an eye for detail, I need your help to tackle a few important tasks:
- Refactoring & Optimization: We're seeing performance caps in our backend logic and database queries. Your mission would be to streamline both these areas, making our Ruby on Rails code run smoother.
- Bug Fixing: Unfortunately, we're experiencing some crashes and server errors. Moreover, there have been some slip-ups with incorrect data handling. We're banking on you to get to the root of these issues and fix them.
This is not an ordinary job. We need a coder with a deep understanding of Rails 5.2.3 and Ruby 2.7.6. Ability to identify and repair performance bottlenecks is a must. Experience hunting down and squashing bugs is a bonus. If you have solid problem-solving skills, and you love a challenge, we'd love to hear from you.
We have an existing app on Heroku that is crashing now due to the number or tenants, rooms and years the data is being queried.
We are looking to update the properties selection box only
* On load nothing in loaded on the left hand side of the properties section i.e. no properties are shown here.
* The box says - "Select your year and number of beds above"
* When the user selects the year, i.e. the current year of 23/24 and 1 or 2 beds etc then at that point we query the data to display the result
Current functionality that must stay the same
* You can select multiple rooms over multiple years - This functionality must stay the same as it is now. The user must be able to display multiple options for number of beds. Each will appear / disappear when toggled using the buttons shown.
* The properties selected appear on the right hand side pannel - This must stay the same as it is now
What must change
* All data rooms and years loaded at once - This is what needs to change
* The search box finds a property - Currently all are loaded at once - New functionality here, the search must still look for all properties but this must only search when someone starts typing. They may search before selecting a year and number of beds option so the search must be able to handle this. It will always default to the current year
* Can we cache these queries to improve speed? If so, this should be updated when a new tenancy is set from booking to complete as we query if a room is available.
I need this asap and we will need to have a conversation on functionality before you start
- Refactoring & Optimization: We're seeing performance caps in our backend logic and database queries. Your mission would be to streamline both these areas, making our Ruby on Rails code run smoother.
- Bug Fixing: Unfortunately, we're experiencing some crashes and server errors. Moreover, there have been some slip-ups with incorrect data handling. We're banking on you to get to the root of these issues and fix them.
This is not an ordinary job. We need a coder with a deep understanding of Rails 5.2.3 and Ruby 2.7.6. Ability to identify and repair performance bottlenecks is a must. Experience hunting down and squashing bugs is a bonus. If you have solid problem-solving skills, and you love a challenge, we'd love to hear from you.
We have an existing app on Heroku that is crashing now due to the number or tenants, rooms and years the data is being queried.
We are looking to update the properties selection box only
* On load nothing in loaded on the left hand side of the properties section i.e. no properties are shown here.
* The box says - "Select your year and number of beds above"
* When the user selects the year, i.e. the current year of 23/24 and 1 or 2 beds etc then at that point we query the data to display the result
Current functionality that must stay the same
* You can select multiple rooms over multiple years - This functionality must stay the same as it is now. The user must be able to display multiple options for number of beds. Each will appear / disappear when toggled using the buttons shown.
* The properties selected appear on the right hand side pannel - This must stay the same as it is now
What must change
* All data rooms and years loaded at once - This is what needs to change
* The search box finds a property - Currently all are loaded at once - New functionality here, the search must still look for all properties but this must only search when someone starts typing. They may search before selecting a year and number of beds option so the search must be able to handle this. It will always default to the current year
* Can we cache these queries to improve speed? If so, this should be updated when a new tenancy is set from booking to complete as we query if a room is available.
I need this asap and we will need to have a conversation on functionality before you start