99 days left...

Maitei Fuerzas de Código rehegua

Hello Codeforces! Can anyone guess the language (Please no google translate)? Comment down bellow! This is day 2 of my blog series

My current plans for the day

I think I should learn a new method.

Also problem 1 in Div.4 is probably is gonna be the new easiest problem on Codeforces. Then goes Watermelon.

(Wonder what problems are gonna be in April Fools)

Div.4

For me, Div.4 was very successful! Surprisingly, I solved the first four easily. But the ratings haven't come yet..

UPD: CREDITS TO Norp!!! MAY EVERYONE HAVE HIGH AND LUCKY RATINGS!!!

Chao to all!

100 Days left...

Hello Codeforces!

Before I can talk about this new blog series, we all have to thank MikeMirzayanov for such an AMAZING website for CP.

How this all started

While I was looking at my blogs I saw a blog "Pupil in 80 days", and I thought "Wow! What an amazing idea for a blog series!". And here is me 10 days later making an amplified version.

My current plans for this day

All I am doing today is solving problems (900 — 1100) to prepare for Div.4.

Help

If any of you have some great TWISTS for this challenge, please comment down bellow.

Credits

So this is credits where I will credit any people who gave ideas in comments and etc.

1. Credits to Norp for the general idea.

If you want to be in the Credits just give an idea. (and I have to accept it);

Chao to all!

Every onewho is div4. (like me): Good Luck! Div4. is tomorrow. hope for every one good luck. also, I wonder what problems are gonna are be in april fools contests?

I was looking in blogs and I saw this blog... I looked at chat, and there was and ISLAMIC terorist. Why are they even in a CP site anyway??? Why isn't MikeMirzayanov doing anything to it? I herd in the news that Islamic terrorists from tajikistan killed about 131 people in Russia (I was very andgry and sad about this news cause I am a tajik). And it is all cause of money. I think MikeMirzayanov should make a username checker for swear words.

Nowadays, I see bad usernames with bad words (exp: f*ck). I think MikeMirzayanov should change the rules about usernames.

I am stuck solving 800 and 900 ratings. What should I do?

mines is 6; whats is urs?

When I was scrolling through YouTube, I saw this video... I just LAUGHED when I watched it full, very funny!

Why??? You might be asking... well, std::endl is the most common thing that might be giving you TLE. It's because std::endl flushes every time. But on the other hand, '\n' only flushes once every 1000 times because is is just a newline character. But if you are used to writing std::endl or endl, you can just make a define for it. #define endl "\n". If you think I am wrong, just comment, don't dislike.

please comment down bellow

The reason that C++20 is better than C++17 is that C++20 is twice as fast when you are using long long because C++20 in codeforces is 64-bit (acording to this blog). The faster we get C++20 the better (if you agree vote : i like it) and please anyone dont dislike me

anyone who knows please comment? also PLEASE RETURN IT MikeMirzayanov (C++20)!!!!!

unsigned long long factorial(unsigned int x) {
    
    if (x == 0 || x == 1) return 1;
    
    return x * factorial(x - 1);
    
}

Macros or also known as #define in c++ are very useful, but it takes a while to think of some great one that will save you a LOT of time, or a little, but it still makes it look better. Like, I was a python programmer and then when I switched to c++, I wasn't used to writing string, so I made a define like this:

#define str string

Here are my personal macros

#define sz size
#define yes cout << "YES"
#define no cout << "NO"
#define str string
#define ll long long
#define ull unsigned ll
#define uint unsigned int
#define pb push_back
#define pf push_front
#define ppb pop_back
#define ppf pop_front
#define vc vector
#define vci vector<int>
#define vcstr vector<str>
#define vcll vector<ll>
#define vcc vector<char>
#define fast ios::sync_with_stdio(false); cin.tie(nullptr); cout.tie(nullptr);
#define fi first
#define se second
#define be begin()
#define en end()

When you start solving a problem, you usually write long pieces of code. #define allows you to shorten and simplifie any ones code. If you want to make a macro for yourself you need to know how to make one first:

// here  we make a define for long long:
#define ll long long

After you do that you can use it anytime you want, for example:

ll a = 98210;

vector<ll> t;

unsigned ll factorial(x) {

if (x == 1 || x == 0) return 1;

else return x * factorial(x - 1);

}

Remember, defines vary from people, you can even get inspired by other peoples #define's too! ask a friend about his defines, they might also be useful for you too!

Everyone wants to make there code FASTER but there is lots of simple solution. the first and most simple one is this:

std::ios::sync_with_stdio(false);

What this does is that usually cout is synced with stdio. so if we set it to false it will make the code slightly faster

Also you can set cin.tie and cout.tie to NULL like this:

cin.tie(NULL);
cout.tie(NULL);

Which will also make it alittle bit faster.