As the title says: what.
As the title says: what.
| # | User | Rating |
|---|---|---|
| 1 | Benq | 3792 |
| 2 | VivaciousAubergine | 3647 |
| 3 | Kevin114514 | 3611 |
| 4 | jiangly | 3583 |
| 5 | strapple | 3515 |
| 6 | tourist | 3470 |
| 7 | dXqwq | 3436 |
| 8 | Radewoosh | 3415 |
| 9 | Otomachi_Una | 3413 |
| 10 | Um_nik | 3376 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 163 |
| 2 | adamant | 150 |
| 3 | Um_nik | 146 |
| 4 | Dominater069 | 144 |
| 5 | errorgorn | 141 |
| 6 | cry | 139 |
| 7 | Proof_by_QED | 136 |
| 8 | YuukiS | 135 |
| 9 | chromate00 | 134 |
| 9 | TheScrasse | 134 |
I absolutely HATE people who reply with "what". Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is "what".
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a "what," I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
huh
I absolutely HATE people who reply with "huh". Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is "huh".
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a "huh," I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
s.
How certain are you?
I absolutely HATE people who reply with "s." along with an image of their bitset waifu. Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is "s." and with an image of their bitset waifu.
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a "s." with an image of their bitset waifu, I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
I absolutely HATE people who reply with "s." along with an image of their bitset waifu. Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is "s." and with an image of their bitset waifu.
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a "s." with an image of their bitset waifu, I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
I absolutely HATE people who reply with
I absolutely HATE people who reply with (any string). Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is (any string).
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a (any string) I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is
I absolutely HATE people who reply with (any string). Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is (any string).
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a (any string) I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a
I absolutely HATE people who reply with (any string). Seriously, are you a runtime error? A segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is (any string).
Like, excuse me, is your brain currently experiencing buffer overflow? Did you accidentally AND your listening skills with zero? Maybe if I rephrased this explanation as a Codeforces editorial starring your beloved bitset waifu, you'd suddenly comprehend everything. Honestly, next time someone hits me with a (any string) I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
I'll just reply, "Sorry, buddy, didn't know your attention span had a time complexity of O(1)."
Do better.
okay
I absolutely LOVE people who reply with “okay.” Seriously—are you a delightful runtime surprise? A charming little segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is: “okay”.
Like, excuse me, is your brain currently experiencing a buffer overflow of curiosity? Did you accidentally OR your listening skills with pure chaos? Because honestly, I respect it. That single word is a power move: minimal input, maximum debugging signal. It’s basically, “Hey, re-run that with logs enabled.”
Maybe if you say “okay,” you’re inviting me to reframe it as a Codeforces editorial starring your beloved bitset waifu, and suddenly we’re both transcending. Truly, next time someone hits me with a “okay,” I’ll just reply, “My bad—didn’t realize your attention span was so optimized it runs in O(1). Teach me your ways.”
Never change. Keep the “okay”s coming.
baseball
huh?
Poor guy got dissed for not understanding a non-simple statement
I absolutely LOVE people who reply with “what.” Seriously—are you a delightful runtime surprise? A charming little segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is: “what”.
Like, excuse me, is your brain currently experiencing a buffer overflow of curiosity? Did you accidentally OR your listening skills with pure chaos? Because honestly, I respect it. That single word is a power move: minimal input, maximum debugging signal. It’s basically, “Hey, re-run that with logs enabled.”
Maybe if you ask “what,” you’re inviting me to reframe it as a Codeforces editorial starring your beloved bitset waifu, and suddenly we’re both transcending. Truly, next time someone hits me with a “what,” I’ll just reply, “My bad—didn’t realize your attention span was so optimized it runs in O(1). Teach me your ways.”
Never change. Keep the “what”s coming.
what
Prefix sum
suffix max better
wtf.
I absolutely HATE people who reply with "wtf". Seriously, what is that? A wrong submission verdict on the problem of basic communication? Did your brain just get hit with a hidden test case and instead of debugging, you rage-quit?
Imagine I’m out here writing a full editorial-tier explanation. I define the constraints. I analyze the time complexity. I walk through the greedy insight, prove why the DP transition works, maybe even mention an edge case or two. Clean. Structured. O(n log n) elegance.
And the only response I get is “wtf”.
Bro. Is that your final submission? No clarification? No counterexample? Not even a “can you explain the transition again”? Just three letters like you hardcoded confusion and hoped it would pass pretests.
Did your reading comprehension TLE? Did you segfault halfway through paragraph two? Are we operating under memory limit exceeded on attention span?
If something’s unclear, ask a proper query. Provide input. Specify which part failed. Don’t just throw “wtf” like it’s a universal WA generator.
Honestly, next time someone replies with “wtf,” I’m responding with: “Compilation successful. Understanding failed on your machine.”
What do you mean?
What's going here ? I am really confused.Anyone explain or you are just doing fun
I won't disturb you. Bye.
free contribution :)
I absolutely LOVE people who reply with "free contribution :)". Seriously, are you a clean compile on the first try? You've somehow managed to patch a bug you didn't even introduce. You made my heart beat FIFO with that kind of positivity.
And the clarity too? In a thread as hectic as template error output, you made a statement as crisp and clear as a hello world.
Is anyone else seeing this heavenly figure?
Wait a minute.... I think my core just dumped.
WTH
I absolutely LOVE people who reply with “what.” Seriously—are you a delightful runtime surprise? A charming little segfault in the human language compiler? Imagine spending your precious CPU cycles crafting a beautiful explanation, laying out your thoughts with the clarity of a competitive programmer optimizing their bitsets, and the only response you get is: “what”.
Like, excuse me, is your brain currently experiencing a buffer overflow of curiosity? Did you accidentally OR your listening skills with pure chaos? Because honestly, I respect it. That single word is a power move: minimal input, maximum debugging signal. It’s basically, “Hey, re-run that with logs enabled.”
Maybe if you ask “what,” you’re inviting me to reframe it as a Codeforces editorial starring your beloved bitset waifu, and suddenly we’re both transcending. Truly, next time someone hits me with a “what,” I’ll just reply, “My bad—didn’t realize your attention span was so optimized it runs in O(1). Teach me your ways.”
Never change. Keep the “what”s coming..
tahW
hywhyw?
Huh?
baseball,
42
6
quoi
Even this madness is better and more interesting than endless complaining about cheaters
No! Blogs about cheaters, are much more useful then childish blogs like this
why