AlekseyL
1 min readJun 4, 2020

--

  1. Point taken. Yep, I preload application, so if I wouldn’t, I assume your point would be correct. But on the prod I don’t see why this is an issue? You can use any kind of patching existing standard library or active support classes and without preloading everything or at least patched part might fail the expectation, so that’s not AR problem. You as the patcher is responsible for proper loading.
  2. My point that you are not obligated in any naming convention of you STI. You can use User > Student, User>Teacher>Chemist, or anything in the naming, and pushing LIKE at the AR level will force you to follow only one way of naming which will pretty fast became too loooong and break “natural language flow”.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

AlekseyL
AlekseyL

Written by AlekseyL

Chief Software Architect / CTO/TeamLead, Ruby and PostgresSQL fan.

No responses yet

Write a response