There's also document.elementFromPoint() which returns only the topmost element.

An interactive playground 👇

js-element-from-point.netlify.app

Patterns aren't free. Every abstraction has a cost.

But it wasn't pragmatic. The "clean architecture" benefits didn't justify the real-world cost. It was optimized for an abstract ideal instead od day-to-day usefulness.

If your "clean architecture" makes the system harder to reason about, it might not be clean at all.

I removed ~40 repositories. More complex queries are now scopes that I can combine, which make for a more flexible design.

Don't get me wrong. I love clean code. Clear separation of concerns. Repositories, mappers, DTOs, the whole circus.

I removed the repositories and fully embraced the ActiveRecord pattern.

All of the repositories only helped to facilitate testing but overall made the design harder to understand and evolve. Another layer of indirection. Cognitive overhead.

- To understand why the code changed, check the commit message and open the ticket for full context.
- Conversely, when reviewing a ticket, you can easily see all related commits.

I worked on teams that didn't do this and I wasted hours trying to figure out why a change happened.

codepen.io/michalsevcik...

gist.github.com/MelkorNemesi...

True that. One of the changes I was very excited about.