2 conferences, 2 continents, 1 big question: what does AI mean for the Ruby community? @maciejkorsan asks questions and @andrzejkrzywda shares what he learned in Brno at Euruko and in Austin at Rails World, and compares the mood in Europe and the US.
youtube.com/watch?v=78lpn1Ob…
New blog post by @maciejkorsan who used Rails to create a collective ambient music experience on @wrocloverb 🎼
blog.arkency.com/teraz-live-…
arkency retweeted
Today was the first time when I used @AmpCode as part of our „AI-native Rails” training
arkency.com/ai-native-rails/
Replying to @andrzejkrzywda
@andrzejkrzywda & @maciejkorsan recap the first day of the camp and discuss what’s coming next for Rails Event Store:
👉 youtube.com/watch?v=tF9cQVk1…
More from RES Camp 2026 is coming over the next few weeks.
Enjoy! 🎬
#RailsEventStore #RubyOnRails #EventSourcing #OpenSource
arkency retweeted
my new ProcessManager gem - finally, the most important DDD building block is simpler to create
blog.arkency.com/3-example-p…
Rails Event Store 3.0 is out — a cleanup release: every API deprecated in 2.x is gone. Plus two new tools.
3.0: blog.arkency.com/whats-new-i…
res CLI: blog.arkency.com/res-cli
res-mcp: blog.arkency.com/res-mcp-ser…
arkency retweeted
I strongly agree with Weaver's "Callbacks Are Not Invariants": callbacks can't keep their promise, writes go through one door.
The ingress doesn't own the invariant. The aggregate does. And the persisted fact, not the outbox, makes effects recoverable.
blog.arkency.com/ingress-is-…
🚀RailsEventStore 2.19.1 is out.
Starting 🔫 for 3.0 — big deprecation wave: old Projection API, apply_* convention, class subscribers, RailsEventStore:: aliases, AggregateRoot::Configuration and more.
Also: functional index for as_of queries. Grab .1, not .0.
Details below👇
arkency retweeted
Your tests are🟢 Would they catch a flipped condition?
I'm speaking at @rbqconf in Texas 2026: "Would Your Tests Catch This Bug? A Mutation Testing Story"
Real Ruby code. Real mutations. Uncomfortable results.
arkency retweeted
There would be no wroclove.rb without our amazing supporters💫
@Arkency has been with us since the very first edition, and we’re extremely grateful to have them on board again this year - thank you for making our conference possible since day one! (1/3)
arkency.com
arkency retweeted
Tip for #RailsEventStore: use `in_stream("stream_name")` in your event assertions:
`expect { ... }.to publish(an_event(X)).in_stream("orders")`
Super helpful once you start using mutation testing (which runs your tests in parallel)
arkency retweeted
deja-vu moment
in 2007 a nontechnical client sent me an app which he just needed to deploy because he vibe coded it on his own (this is a story how @arkency started btw because he suggested this name)
today in 2026 a nontechnical client sent me an app which he thinks is ready to be deployed because he vibe coded it
in 2007 the equivalent of vibe coding was Rails
of course at none of this case it was only about deployment, the apps need some
fixing
fun times again 😎
arkency retweeted
Ruby 3.4 warnings led me to refactor 100+ Slack message methods.
What started as a frozen string literal fix ended with a 20-line class that sparked joy.
Sometimes the simplest abstractions are the most satisfying.
blog.arkency.com/the-joy-of-…
arkency retweeted
Pessimistic architecture - that was my thought when reading this book.
Non-functional requirements are often ignored by architects and programmers. Yet, it's them which can kill your app and your business.
Residuality is a concept described by Barry O'Reilly, a very intriguing set of heuristics to help build an architecture that can survive many "stressors".
Looking forward to find stressors and build the matrix for our current projects.
If you need a challenge to your current architectual status quo - this might be the book to read.
I recommend to read it in the form of a book reading club, as we did at @arkency - the concepts are not so easy to digest alone.
Multi tenant applications with horizontal sharding and Rails Event Store - a practical guide: 🔗 blog.arkency.com/multi-tenan…
arkency retweeted
Pretty happy with my narration for the Rewrite vs Modernize webinar
In most cases modernization is a better option. But why? How to convince the management? What are the best techniques you should know if you need to do the modernization?
See you there?
arkency.com/webinars/rescuin…












