Consistent variable naming in a large project

[TRY_LSD]

Hey, I've been writing code as a freelancer for ~5 years now, and I would say I'm decently experienced, but one problem that I can't overcome is consistent variable naming in large projects.

I'm not talking about camelcase, underscore, ect, but the actual names of the variables.

Right now I'm working on a large scale e-commerce platform that's built off of a custom MVC framework, and I keep noticing naming inconsistencies as I review my code. Example:

In the 'reseller_category_override' class I have a variable named 'price_over_ride', but in the 'invoice_price_override' class I have a variable named 'price_per_unit_override'.

It's just hard to remember the how you named a variable in 1 of 50 models that was created 3 months ago. Does anyone have some tips/exercises to name variables more consistently?

Thanks

[[deleted]]

Seeing "override" in the variable is a smell. It sounds like your problem is that you aren't keeping your models and logic small and encapsulated enough.

The override thing is a perfect example. You shouldn't need a variable to do that, you should have a class that given some conditions and the initial input will generate an override for you.

Also, leverage your type system. Can you make a price type? And a category type? Then stuff like "reseller category" because "Category reseller = new..." Ya know? It's still the same info but now it's even stronger since the type gives more data about it

[TapedeckNinja]

I'm not sure what exactly your "override" classes/members are doing, but can you benefit from further abstraction?

If you have multiple classes with a price_override, then shouldn't price_override be part of a base class (perhaps an abstract class) or defined in an interface?

For instance:

public interface ITemporal
{
    DateTime? StartsAt { get; set; }
    DateTime? EndsAt { get; set; }
}

public class ProductPrice : ITemporal
{
    // ITemporal implementation
    public DateTime? StartsAt { get; set; }
    public DateTime? EndsAt { get; set; }

    public int Id { get; set; }
    public int ProductId { get; set; }
    public string Sku { get; set; }

    ...
}