f0b473e1-c892-4a21-8319-68f56f713c0d

[giscus[bot]]

f0b473e1-c892-4a21-8319-68f56f713c0d

Generic names like "manager" are easy and can trick us into thinking they are good for consistency. But they can quickly undermine conveying the meaning of your code.

https://www.ssw.com.au/rules/avoid-generic-names/

[wicksipedia]

💯 - project names like shared and common come to mind as well, they are horrible since they become a catch all receptacle

[Calinator444]

Well I guess it's time for me to rename this then

type PageData = {
  filename: string;
  isNewConsultingPage: boolean;
};

[chrisschultzssw]

This is important because it's an easy one to miss - generic names will make sense when you create them, but to other devs (or future you) they will not be clear at all.

[ncn-ssw]

I regard this as the most important tip, as this can lead to costly misunderstandings about what a section of code achieves.

[bahjatalaadelssw]

It's important to take the time to label anything with a meaningful title, it helps with searchability and clarity.

[thom-wang]

I used to write things like Helper and Manager a lot because it is generic and you can put everything in it easily. After this I came to realize it is really hard for other devs to read it afterwards and I'll change them to specific meaning names instead.

[babakamyljanovssw]

Good naming the services or handlers are really important to understand what functions they are responsible for.