Though ideally if we use the views correctly and override them well, Drupal Views itself take care of getting the translated version as per configurations of the view. For details check this: EntityField::getValue
Drupal Planet
A lot of times we come across a requirement where we need to manage some additional data for the Drupal entities. Now, if we think simply, the solution is to create fields .. right... easy and best, that's what Drupal is all about, entities and their properties as fields. But, there can be scenarios where the entity is not fieldable (as of now).
Most of us know, the ideal way of making a variable available in a specific twig file is to use hook_preprocess_HOOK. But what if we have a requirement that we need a kind of global variable that should be accessible in any twig file. So, that we are able to use it wherever we want to, without additional pain.
The best part of Drupal is, everything is possible. But at the same time, there is a trick, you always have more than one way of doing things. And now it's in your hands to pick up the best suitable performant way for your solution.
Recently completed Acquia Backend Specialist Certification thought to share my thoughts around this certification exam that might help the aspiring ones. While preparing for this exam, I had heard that this is the toughest exam out of all the Acquia Drupal Certifications and in my opinion, this rumour is true.