The missing Ruby on Rails architecture

🧵let me explain the 10 rules here 1. App layer vs domain layer

Assume that controllers and service objects are app layer (a bit simplification here, but bear with me).

Service objects can never call each other. They are the application facade.

Let's fight this monster

/thread First rule: test coverage, no changes can be made if you're not secured
ideally with mutation testing showing us alive mutants

my definition is that nocode/lowcode can be used by non-programmers

I hate to make marketing based on the virus situation, but people keep asking me about async/remote work tips and most of the questions are answered in our (@arkency) "Async Remote" ebook.

blog.arkency.com/async-remote/ Additionally, there are our "remote", free blogposts here - blog.arkency.com/tags/remote/

threads in slack are NOT async-friendly 1. someone writes a channel message (M)
2. I read it, interesting, but not much to add from me, yet
3. I go to focus on my task, turn off slack
4. other people add new messages to that channel, less related
5. the original message M is now one screen/scroll behind

Ruby AOP experiments with #prepend

Using prepend + super we can simulate the AOP's before advice now the same, but with refine

My favourite time - books around and researching new/old architectural ideas

Have you signed up to my tomorrow’s Rails Architect webinar already?

There will be:

OOP
FP
DCI
AOP
microservices aka distributed objects

and more

with practical examples arkency.com/webinar/

I'm looking for OSS projects (Ruby for a start), where there are issues which can be implemented by a fresh Ruby dev (let's say after bootcamps).

The idea is to connect Ruby bootcamp graduates with OSS mentors.

RT please for now this is only a theory, but the assumption is:

- the graduates benefit by having "real" Ruby work to do, with a mentor for such task

- the OSS mentors benefit from potential new contributors/contributions

- the world benefits from having better educated developers

1/

In our recent @arkency survey - the clear winner for the question - “what is the most painful part of big rails apps on which you worked on” - was a short answer:

“Callbacks”

Do you share the experience? 2/

I wonder if we can get more specific here...

What kind of Rails callbacks are popular in the wild?
The ones to send emails?
The ones to update some other ActiveRecord objects?
Something else?

2 fuckups from my webinar

1. the mic from the closed laptop instead of from ext monitor

2. I didn’t see messages from people (terrible UX) first 10 mins were probably still ok, but then the laptop fans went on making it terrible