cargo is a bad example as it's universally `cargo build`.
Make on its own is great but most of the time I've worked with C projects it's been cmake/autotools + global pkg installs, which you Do have to frequently look up.
Parent states that it's always "cargo build" which in 90% of the cases, is true.
Except for the projects that would require something like "cargo build --feature=wayland" for example, in order to run.
So "cargo build" ends up not being universal, and adding make will make it just "make build" regardless of what flags people use with cargo, meaning it's more universal than "cargo build".
Except if you want to use some specific feature. Or specific log level. Or build a specific crate in a workspace. Or...