The difference between Essential complexity and Accidental complexity (in the context of development with Ruby on Rails)

Does your Ruby on Rails app has Layered Architecture?

I just gave my talk “The Shape & the (Missing) Idea of Service Object” at #EuRuKo2024 Service Object is a FAKE concept. I share a lot of my learnings here: rails.services

They should start early these days!#EuRuKo2024

Slides from my Lightning Talk at #EuRuKo2024 : speakerdeck.com/inem/code-topo… Code Topology (Dummies) Notation - a way to express code complexity and architecture with pictures of little dummies:

Looks like a bit too much of attr_accessors!

#EuRuKo2024 Dave Thomas: “Service Objects is the most ridiculous concept ever invented in Software Development!”

3 Painless Rails complexity management principles you need to adopt while your app is still small: 1. Use distinct building blocks for each type of work your code is doing 2. Ensure your layered architecture is truly layered 3. Stick to the single level of abstraction principle!

The only idea of Service Objects is their shape. And because of the similarity of the shape, developers consider them a meaningful type of building block in their apps, which they are not.

You: carefully planning the migration from (database-based) Delayed Job to Sidekiq. Rails devs around: Sidekiq? That’s so 2020… We're moving to (database-based) Solid Queue now. reddit.com/r/rails/commen…