Ivan Nemytchenko

I help SaaS startups build anti-fragile systems with a lean development process using the Painless Rails approach | CTO at

[Ivan Nemytchenko @inemation]

@strzibnyj I'd say Replit

[Ivan Nemytchenko @inemation]

AI-coding for me in 2025:

- 13 Cursor windows
- 8 Claude Code sessions across random Terminal windows
- Ports 8001-8005 all mysteriously occupied
- Moved project to a new folder → lost Cursor/Claude history

[Ivan Nemytchenko @inemation]

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.

https://t.co/nhfcn72pMX

[Ivan Nemytchenko @inemation]

These are purely theoretical speculations, though. I’d love to hear from people with experience in both Rails and Next.js.

[Ivan Nemytchenko @inemation]

Development on Rails is 2 times faster than with Next.js?

I have never tried Next.js, but I am curious about all the fuzz around it. So I decided to ask ChatGPT to compare amount of work needed to develop primitive Twitter clone using both. Here’s what I’ve got:

[Ivan Nemytchenko @inemation]

It seems it boils down to whether you’re building a frontend-centric product or not.

If you are, and you have an experienced frontend team, you might achieve development speed comparable to Ruby on Rails.

[Ivan Nemytchenko @inemation]

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.

[Jason Swett @JasonSwett]

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

[Ivan Nemytchenko @inemation]

@rockatanescu Yes, of course. I am not questioning 95% of what she’s saying. My only concern is that the framework _could_ do something to help organize large codebases, but it doesn’t.

[Ivan Nemytchenko @inemation]

Here’s mindmap of @eileencodes talk about Modularised Monolith at #RailsWorld 24. I wasn’t lucky (or I was?!) to work on a codebase similar in size to @ShopifyEng, but many things sound familiar. Many teams start facing such issues with Rails when they reach 50-100 models.

[Ivan Nemytchenko @inemation]

My high level guiding principles:
https://t.co/9AsKhfi7II

[Ivan Nemytchenko @inemation]

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!

[Ivan Nemytchenko @inemation]

The best thing you can do in this situation is to think about such guiding principles yourself.

Hint: To wrap everything into service objects is not a good guiding principle.

[Ivan Nemytchenko @inemation]

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!

[Ruby on Rails @rails]

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 fix? Is this better than before?' https://t.co/qPYcMCKJcN

[Ivan Nemytchenko @inemation]

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

[Ivan Nemytchenko @inemation]

Looks like a bit too much of attr_accessors!

[Andrei @rushing_andrei]

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

[Ivan Nemytchenko @inemation]

Slides from my Lightning Talk at #EuRuKo2024 : https://t.co/7BQZgz7MXa

Code Topology (Dummies) Notation - a way to express code complexity and architecture with pictures of little dummies:

[Ivan Nemytchenko @inemation]

They should start early these days!#EuRuKo2024

[Ivan Nemytchenko @inemation]

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: https://t.co/Yy3wkqHy1p

[Ivan Nemytchenko @inemation]

This post touches the very basics of Ruby OOP, but I'll add more complex topics pretty soon.
- Basic OOP anti-patterns
- Dependency injection
- Subtype polimorphism
- Structs in Ruby

[Ivan Nemytchenko @inemation]

I start all my conference talks with this these days:
https://t.co/Q7eKCZJnmt

It's damn convenient and allows me to discuss any tricky abstract Software Engineering concept in the most concrete way possible.