@inemation Profile picture

Ivan Nemytchenko

@inemation

I help SaaS startups build anti-fragile systems with a lean development process using the Painless Rails approach | CTO at https://t.co/i2ugUwIhZv

Similar User
arkency photo

@arkency

Xavier Noria photo

@fxn

Maciej Mensfeld photo

@maciejmensfeld

Peter Solnica photo

@solnic_dev

Janko Marohnić photo

@jankomarohnic

Maciek Rząsa photo

@mjrzasa

Robert Pankowecki photo

@pankowecki

Szymon Fiedler 🇵🇱 photo

@szymonfiedler

Adam Piotrowski photo

@pan_sarin

Oskar Szrajer photo

@oskarszrajer

Anton Paisov photo

@antonpaisov

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.

Service objects aren't a solution, they're a style. Putting something in a service object doesn't on its own necessarily fix anything.



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!

At a certain scale, a company may ask: 'Should we stay the course with a monolith or migrate to microservices?' At @Shopify they chose to modularize their monolith, but after 6 years @eileencodes wonders in her #RailsWorld Day 2 Opening Keynote: 'Did that fix what it set out to…

Tweet Image 1


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

Tweet Image 1

Looks like a bit too much of attr_accessors!

@inemation Have you seen this ugly service object standing right outside of the @euruko conf? 😄

Tweet Image 1


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:


They should start early these days!#EuRuKo2024

Tweet Image 1

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

Tweet Image 1
Tweet Image 2
Tweet Image 3
Tweet Image 4

Does your Ruby on Rails app has Layered Architecture?

Tweet Image 1

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

Tweet Image 1

Is it a secret information on how many models and controllers there are in Basecamp and Hey apps? I am very curious about it. Feels like it could be easily less than 100 models in Hey app.


In Ruby on Rails application what is the Model Layer for and what is it about? (pls RT)


Ivan Nemytchenko Reposted

Great presentation by @inemation at @wrocloverb debunking the Service Object pattern. Thank you for teaching me how to do forms with the “active_form_model” gem as well.

Tweet Image 1

What is your reason to use Service Objects? Is there a smarter rationale than “Our controllers got big and we had to move stuff elsewhere”? cc @wrocloverb


Seriously considering to switch to SQLite in production for personal projects after the talk of @fractaledmind at @wrocloverb’24.


Loading...

Something went wrong.


Something went wrong.