A Java/Spring developer shares their experience learning Ruby on Rails for a client project. The post covers Rails' core principles (convention over configuration, DRY, full-stack defaults), practical features like generators, Active Record associations, and the Rails console, and draws a direct comparison with Spring Boot. The author describes a love-hate journey — initial delight at productivity, frustration when the magic broke, and eventual appreciation for Rails' opinionated efficiency. Key takeaways include Rails' strength for rapid prototyping and MVPs versus Spring's enterprise robustness, and the trade-offs of implicit convention versus explicit configuration.
Sort: