About Me:
I have 10 years of professional experience with Ruby on Rails. A friend introduced me to ruby in my final year of college. Its simplicity drew me in - it was refreshing to see that something as basic as adding numbers was as straightforward as 1 + 1, a stark contrast to my experience with C. Since then, I've loved building products in Ruby and Rails.
In my early career, one of the first major challenges I faced was n + 1 queries. This issue was causing application crashes and out of memory errors. Following articles/stackoverflow/rails guides lead me to use "includes" but I quickly realized that sometimes Rails’ magic isn’t enough -
sometimes you actually need to jump, get your hands dirty and dig deeper. This meant writing raw SQL queries which was learning in itself, and sometimes it means that problems initially looks complex but actually they are as easy as like removing the redundant http requests.
Navigating through those challenges taught me a lot about the importance of optimizing for scalability and maintainability.
More recently, at Toptal, while working on an analytical tool, I designed a module in the application's code structure with a focus on modularity and ease of extension. This approach ended up being so helpful that we decided to create a Rails generator to speed things up even more. The generator creates the necessary files with boilerplate code, so all that’s left is to adjust them to fit the specific requirements. It saved us a lot of time on repetitive setup tasks and made development much smoother. Read more here - https://medium.com/@ahmadhamza/scalability-through-conventio...
This journey—from discovering Ruby’s simplicity to now writing scalable applications—has been incredibly fulfilling, and I’m always looking to push those boundaries further.
About Me: I have 10 years of professional experience with Ruby on Rails. A friend introduced me to ruby in my final year of college. Its simplicity drew me in - it was refreshing to see that something as basic as adding numbers was as straightforward as 1 + 1, a stark contrast to my experience with C. Since then, I've loved building products in Ruby and Rails.
In my early career, one of the first major challenges I faced was n + 1 queries. This issue was causing application crashes and out of memory errors. Following articles/stackoverflow/rails guides lead me to use "includes" but I quickly realized that sometimes Rails’ magic isn’t enough - sometimes you actually need to jump, get your hands dirty and dig deeper. This meant writing raw SQL queries which was learning in itself, and sometimes it means that problems initially looks complex but actually they are as easy as like removing the redundant http requests.
Navigating through those challenges taught me a lot about the importance of optimizing for scalability and maintainability.
More recently, at Toptal, while working on an analytical tool, I designed a module in the application's code structure with a focus on modularity and ease of extension. This approach ended up being so helpful that we decided to create a Rails generator to speed things up even more. The generator creates the necessary files with boilerplate code, so all that’s left is to adjust them to fit the specific requirements. It saved us a lot of time on repetitive setup tasks and made development much smoother. Read more here - https://medium.com/@ahmadhamza/scalability-through-conventio...
This journey—from discovering Ruby’s simplicity to now writing scalable applications—has been incredibly fulfilling, and I’m always looking to push those boundaries further.