#define int long longis definitely S tier

itn = int , sigma = signed and int = long long is 100% S+ tier

This is 100% S+.

#define ll long long

#define all(x) x.begin(), x.end()

#define rall(x) x.rbegin(), x.rend()

#define yes cout << "YES\n"

#define no cout << "NO\n"

#define debug cout << "Debug\n"

#define int23_t long long definitely traumatized me...

S+ defines which i use
D all the rest

#define pofik continue in c tier is crazy

I do #define long long long because I like being chaotic

S+ tier

// ultrakill reference???
#define gabriel cout<<"Machine,\nI will cut you down,\nbreak you apart,\nsplay the gore of your profane form across the STARS!\nI will grind you down until the very SPARKS CRY FOR MERCY!\nMy hands shall RELISH ENDING YOU\nHERE\nAND\nNOW!"; 
// brutal diff gabriel 2 in 45 secs p rank
#define int long long
#define endl '\n'
#define all(v) v.begin(),v.end()
#define idc continue
#define itn int
#define I i
#define ,= <=

I'd go for #define ll int

I generally prefer doing something like using ll = long long; (actually, using ll = int64_t;) instead of #define ll long long because the later option doesn't admit functional style casts (in other words, long long (val) does not compile). Also, semantically speaking it is much nicer.

Additionally, #define int long long is quite evil from my perspective and I only use it in worst case scenarios. The reason why I don't appreciate it is that it admits laziness in terms of reasoning about types. Reasoning about types can often make you understand the problem and your solution better, which means that fixing bugs later on becomes easier (that is to say, if you have a better understanding, your code becomes more "maintainable" for you).

I used to have this:

#define FOR1(a) for (ll _ = 0; _ < ll(a); ++_)
#define FOR2(i, a) for (ll i = 0; i < ll(a); ++i)
#define FOR3(i, a, b) for (ll i = ll(a); i < ll(b); ++i)
#define overload3(a, b, c, d, ...) d
#define FOR(...) overload3(__VA_ARGS__, FOR3, FOR2, FOR1)(__VA_ARGS__)
#define RFOR1(a) for (ll _ = ll(a) - 1; _ >= 0; --_)
#define RFOR2(i, a) for (ll i = ll(a) - 1; i >= 0; --i)
#define RFOR3(i, a, b) for (ll i = ll(b) - 1; i >= ll(a); --i)
#define overload3_r(a, b, c, d, ...) d
#define RFOR(...) overload3_r(__VA_ARGS__, RFOR3, RFOR2, RFOR1)(__VA_ARGS__)

The usage is like:

FOR(n) // iterates n times
FOR(i, n) // iterates i = 0 to i = n-1
FOR(i, 1, n+1) // iteraties i = 1 to i = n

And you can use the same thing to iterate backwards by using RFOR. As it was not really a good practice, I stopped using it lol.

The best one for me was:

#define victor vector<int>

The defines in this submission should be on S++ tier.

#define REP(i, a, b) for(int i = (a); i <= (b); i++)
#define PER(i, b, a) for(int i = (b); i >= (a); i--)

Когда-то мне нравились такие)

Wait, no body uses typedef?

how can i get this ranking/order that you made,
when i click cf's image it has very few pixels.
when i click the tierlist link it is not ranked

One of my define:

#define fast_io ios_base::sync_with_stdio(false); cin.tie(0);

#define pb push_back