Hm, if you mean software design patterns, then not exactly. It's probably harder to detect in just coding world, but the easiest one I can think of in our realm "checking current CPU usage of X service". In my current company, there are quite a few ways - logging into AWS -> switching to production environment -> going to ECS -> Looking up the service -> Clicking on metrics, or opening DataDog -> Dashboards -> Service Name.
I understand it's very reductive and simplified, but for every task there are alternative ways to reach the goal, and from my historical experience, everyone does everything differently. Some things can be optimized significantly, if others just knew about the possibilities.
I understand it's very reductive and simplified, but for every task there are alternative ways to reach the goal, and from my historical experience, everyone does everything differently. Some things can be optimized significantly, if others just knew about the possibilities.