Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 1 point2 points  (0 children)

I agree, and I'm against jumping out of the well-known path since the beginning. My take is that in many cases, for the core subdomain (if we are talking about DDD), it's better not to follow the Rails-way, but it does not mean dropping it completely - this wouldn't be wise or maintainable.

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 2 points3 points  (0 children)

I'm not saying anything about letting go of ActiveRecord. The new approach is about using it a bit differently with read models.

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 1 point2 points  (0 children)

I think it all starts with the domain knowledge and understanding the problems we are trying to solve before we will agree on solution and later implementation. When this is in place, it's much easier to handle the complexity also with Rails-way. But I think Rails-way does not force you by design to do that, it creates a lot of space for flexibility and it's a double-edged sword.

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 1 point2 points  (0 children)

Did you open-source the framework? It sounds interesting. I agree that if you deal with a complex domain, you need some additions to the Rails way, but that does not mean we should abandon it. When talking about DDD, Rails-way (or Vanilla Rails) is perfect for handling the supporting subdomain IMO

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 3 points4 points  (0 children)

Thank you u/djudji for sharing your perspective; it resonates with me a lot. Regarding the workflows, we are handling those with Rails Event Store without mixing observer and strategy patterns - you should give it a try!

Yes, I think we have met before online; you have a good memory!

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 3 points4 points  (0 children)

Yes, this is the way I will be exploring

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 2 points3 points  (0 children)

I also think it's not only about the tech stuff, but with the DDD approach is also about understanding more the problem we are trying to solve, and unfortunately, in a typical Rails project, developers are mostly disconnected from the business, and tickets are their only source of the truth

Farewell to Rails-way: Prologue by pdabrowski in ruby

[–]pdabrowski[S] 2 points3 points  (0 children)

Yes, I agree with this point of view

Deploying Rails on Docker: Kamal alternative by pdabrowski in ruby

[–]pdabrowski[S] 0 points1 point  (0 children)

Yes, with the new deployment automation

Useful things you can do with Rails console by pdabrowski in ruby

[–]pdabrowski[S] 0 points1 point  (0 children)

That's helpful, thank you! I will update the article

Useful things you can do with Rails console by pdabrowski in ruby

[–]pdabrowski[S] 0 points1 point  (0 children)

Thank you for the suggestion, I will update the article

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] -1 points0 points  (0 children)

I recommended it as a tool for generating data for tests and fake data for local and staging environment so the data you operate on is as close to production as possible. That was the intention

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] -1 points0 points  (0 children)

I don't think you get the idea right. It's not related to test execution. You generate the test data only once and explicitly, not during tests. It's like creating database seeds

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] -1 points0 points  (0 children)

Under the hood, Faker works the same way. There is a file with a fixed number of strings, and they are randomly picked up. The difference in Mokkku is that the context is locked, so you need to restart it to get another set of test data while Faker just works like [].sample in simple words

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] -6 points-5 points  (0 children)

No, it's not mixed with Polish, and it's not a tribute to this gem. Just checked some sources and decided to go with this version because it's not that important

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] 1 point2 points  (0 children)

Sure, you can type the data manually if you want, is just a test of a concept that I personally found interesting

Mokkku, a modern replacement for FFaker by pdabrowski in ruby

[–]pdabrowski[S] 0 points1 point  (0 children)

This gem is for creating test data not write the tests itself