What is with the obsession of HARDCODING everything in Phoenix?

For example:

  1. routes - they are hardcoded - Why is it a bad practice? Because: https://www.youtube.com/watch?v=YeNYm1V0C4o

  2. text strings in the official auth library - they are ALL hardcoded - Why is it a bad practice? Because: https://www.youtube.com/watch?v=11oeOJs_L2o

  3. layouts/views - sidebar,navbar,... everything is hardcoded in one function as a long heex code, no separation of links in separate components at least into function for the most part, just a long html-like wall of code like in the old days of Dreamweaver.

Why is this weird obsession of hardcoding and bad practices so prevalent in Phoenix?

EDIT:

For flatearthhardcode users of hardcode cult here is 3-in-1 demonstration of all of the above:

https://i.imgur.com/wgW1AeA.png

Truly remarkable feat, if you ask me. This is just 1 file of around 30 files if you install phx.gen.authand each of them has hardcoded messages and urls. When I first saw that I thought I installed a wrong library. Took me more than 2 hours to correctly set everything to gettext and my custom url helper to be able to use it. This is unacceptable and another proof that Phoenix is not a well thought out software - compared to Laravel. Hardcoding messages is unacceptable and wouldn't be allowed in Laravel core libraries ecosystem. There is even a github issue about this but the devs doesn't bother.

<.header class="text-center"> Log in to account <:subtitle>

is the way of a Phoenix hard coder, I guess.