655+ Problems | Multi-Platform | Serial Progression
This roadmap is designed for someone with ~800 Codeforces rating who wants to systematically level up. Follow problems serially from #1 onwards - the order is carefully crafted so each problem builds on previous concepts.
| #include <bit> | |
| #include <cstdint> | |
| #include <limits> | |
| // Positive, finite, normal binary32 inputs only. | |
| float invsqrt_fast(float x) { | |
| uint32_t i = std::bit_cast<uint32_t>(x); | |
| int64_t u = int64_t((i ^ 0x800000u) & 0xffffffu) - 0x7e3500; | |
| int64_t a = u < 0 ? -u : u; | |
| int64_t p = -181511850 + ((65*a) >> 1) + ((u*(0x1700000 - 3*a)) >> 21); |
The following are examples of the four types rate limiters discussed in the accompanying blog post. In the examples below I've used pseudocode-like Ruby, so if you're unfamiliar with Ruby you should be able to easily translate this approach to other languages. Complete examples in Ruby are also provided later in this gist.
In most cases you'll want all these examples to be classes, but I've used simple functions here to keep the code samples brief.
This uses a basic token bucket algorithm and relies on the fact that Redis scripts execute atomically. No other operations can run between fetching the count and writing the new count.
Un keylogger éducatif et léger écrit en Python, équipé d'un mode discret automatique et compilé sous forme d'un unique fichier exécutable (.exe) Windows grâce à Nuitka.
Pour packager ce script, vous devez utiliser Python 3.9 (64-bit) sur un environnement Windows.
| #!/usr/bin/env python3 | |
| """ | |
| Samsung NVMe Firmware Decryption Tool | |
| Decrypts official Samsung firmware for use with nvme-cli on ARM64/RISC-V/etc. | |
| Only works with official Samsung firmware - cannot be used for modification. | |
| The AES-256 key must be extracted from the fumagician binary: | |
| strings fumagician | grep -E '^[A-Za-z0-9+/]{43}=$' |
name: writing-whip description: >- Kill all AI writing tropes and behaviours at the source: generation. Focus on quelling behaviour-driven triggers. Load before writing, especially for anything longer than a paragraph and re-check output against it, extremely important for communications, documentation, outbound, client-facing copy and for your own replies to the user. metadata: category: writing author: Ossama Chaib
| #!/usr/bin/env bash | |
| # AppID is a special case I haven't made generic yet since it doesn't have an end byte the same way other fields do afaik | |
| # Adapted from my gist: https://gist.github.com/sonic2kk/4a3383b401931a171a4addc29bdf903f | |
| function get_shortcut_appid { | |
| # Magic that represents 'appid' column | |
| magic_appid="617070696400" | |
| shortcut_hex="$1" | |
| function convert_aid { |
