Blog

A simple LeetCode problem becomes a great example of Ruby’s philosophy: expressing what you want instead of how to do it. In this post, we compare a traditional hashmap implementation of Valid Anagram against Ruby’s incredibly concise chars.tally approach and explore why Ruby solutions can feel almost suspiciously elegant.

A simple LeetCode problem turned into a surprisingly good lesson in both algorithms and Ruby itself. From brute force nested loops to hash-based Sets to Ruby’s almost suspiciously concise uniq.size solution, this problem highlights how the same challenge can evolve as you learn both performance optimization and the philosophy of the language.

A backend engineer used to Java dives into Ruby syntax for the first time. From guard clauses and enumerable chaining to symbols, blocks, and lambdas, this is a look at the moments where Ruby initially felt confusing, surprisingly elegant, and occasionally completely cursed.

I wanted to build a personal platform that felt simple, maintainable, and fully my own. What started as curiosity around Ruby on Rails became a self-hosted portfolio and blogging platform built with Rails 8, PostgreSQL, Hotwire, Tailwind, GitHub Actions, and a production deployment running entirely on a personal VPS.

A distributed systems engineer explores Ruby on Rails after years of building cloud-native backend platforms, event-driven architectures, and microservices. This post begins a journey into a different philosophy of software development — one focused on simplicity, developer productivity, and understanding why Rails continues to resonate with so many experienced engineers.