Rails. Fucking rails...

God damn monoliths, built by a cowboy coder.

Every one I have ever worked with becomes (or already is) a house of fucking cards that will blow over at the slightest gust of wind.

The worst part is that you always hear the same justifications from rails developers, then after they convince the higher-ups that “we will build it right, not like those other monoliths” we find ourselves F’ed right in the A a few months later.

It’s this frustration that lead me to MUCH better paradigms like Microservices, Event-Sourcing, CQRS, Domain Driven Design and the like.

When someone says “our backend is in rails” my first response is “so when are you replacing it?”

So... Yesterday I ordered a meal and it had whole jalapenos in it. I didn't order jalapeños. I love the taste but I hate toilet visits after. Hence, was putting them aside. But then I got into that new code, jumping around this new project I'll be working on. We were getting intimate. I liked the architecture, I liked it a lot - it was using event sourcing and respected CQRS. Suddenly I realised I ate everything. Including jalapeños. And the only reason I noticed is because I was eating with my hands. And my eye got watery. And I wiped it.

So, yeah. Yesterday for the first time in my life I was pouring milk into my eyes. Does this count as a proper dev rant? I don't know. Fuck the protein interface that can't process simple food orders, though.

So I’m like 90% certain 10% of my app should be event sourced, and the other 90% CRUD based (but event driven).

However after trying to tackle this from a variety of angles I’m 100% ready to jump off a building

So I’m taking a break and eating a fucking donut

Working with technologies that excite me, which at the moment would be functional programming, CQRS, Event Sourcing, and the actor model, with a side of machine learning and serverless architectures. At a company that is large enough to pay well and grow in, but small enough that my contributions are recognized and appreciated. Or even better, one that I own and run.

I’ve been building event-based systems for a few years.

Now I am with a company building MVC apps with ruby-on-rails. (Well, actually the V is handled by React)

To all the the good Rails developers out there:

What advice do you have to getting into this thing very fast. I’ve got video courses from UDemy and the docs but are there any hidden diamonds in the rough out there I should check out?

Just learned about event sourcing and CQRS. I think I'm in love

Just saw this talk on event sourcing. Kind of amazed by the benefits of this, and that I haven’t really touched upon it previously. Would have saved me a lot of trouble in the past year. Anyone have any ranting/thoughts about this?

CQRS + Event Sourcing.

Because it just makes sense. In small applications, just command pattern, but CQRS and Event Sourcing is a beautiful, beautiful thing.