A Good Naming Convention for Routes, Controllers and Templates?

JoliCode - JoliCodeBlog - 04/09
I’ve had my fair share of web projects during my career, and with experience building up, I’m increasingly pushing for coding standards, conventions, and naming precision in my code reviews. A badly named service, a variable giving no clue, a namespace that makes no sense, multiple
Cet article est aussi disponible en 🇫🇷 Français : Une bonne convention de nommage pour les routes, les contrôleurs et les templates ?.

I’ve had my fair share of web projects during my career, and with experience building up, I’m increasingly pushing for coding standards, conventions, and naming precision in my code reviews.

A badly named service, a variable giving no clue, a namespace that makes no sense, multiple names for the same concept: it all makes reading code harder and demands a greater cognitive effort than I can afford 🤣 That’s called visual debt.

Today, I want to write about the naming involved in a standard route/controller/template web framework (examples will be Symfony but this applies to Laravel, Django, etc).

Consider this:

  1. We need to display a list of products on /produ...
    [Courte citation de 8% de l'article original]