+1 for this, code should be layout to express business logic, abstractions that difficult the readability of the business logic are not worth it, it is a distractions. Yeah takes a while for juniors to understand when/how to use DRY.
Repetition is not a terrible evil, it has its place
As a Brazilian who migrated to another country, I mostly try to hide my background. It is great to see that some of our values, like compassion, are appreciated in other countries, and folks like Luiz André could show a bit of it
I have a reolink E1 hooked to my Homeassistant, the rstp stream seems to crash from time to time. I had never heard of neolink, would it help on this case?
True, you could implement Ecto exactly in Ruby, except you'd be writing effectively Elixir and every library released that got close to this in the 15 years I've been doing Ruby has been either disliked or disregarded. Each with less contributor activity in their lifespan than a month of ActiveRecord attention.
Yeah, the example is Rails-specific but Ruby is full of methods that mutate existing state. Most of the time they're marked with `!` at the end, but not always.
I was interviewing for a job earlier this year, things were going well and I made it through various stages. I was scheduled to come in to do a face to face interview with the team, and the interviewer said "be sure to wear a suit".
I noped right out of that. Told them I was not interested.
Good to hear it