req and res are two good candidates too! Especially when you start caching, fetching from backend and api… resFromServ, resFromCache, resFromNetwork etc. make things much easier to understand!
I've been coding for over 20 years now! (WOAH, do I feel old)
I've touched just about every resource imaginable under the Sun (too bad they were bought out by Oracle)
reqandresare two good candidates too! Especially when you start caching, fetching from backend and api…resFromServ,resFromCache,resFromNetworketc. make things much easier to understand!I really like this example, good call out😉
It is until it isn't. This is one of the large problem with the suggestion to use shorthands, is they mean different things to different people.
Coming from a Win32 background, "res" is a "resource", such as icons, images, etc. They're non-code elements compiled into a file exe file.
Its easy to get keyword conflictions between people when shortening them like this.