They Don't Know I Have A Computer Science Degree

Content 3 HOURS LATER Thanks for watching my Live Coding Stream TOREG, Byece VIEWERS: O

Content Linked List data structures be like: I know a guy who knows a guy

Content How I treat PROD servers How I treat DEV servers Oh dear, oh dear. Gorgeous. You fucking donkey.

Content Unbelievably Wave-Function Badass Collapse Neat Acronym ACORN GRASP OPTICS VEGAS Brute-force Double Metaphone Fibonacci Search Genetic Algorithm Gray Code Gnome Sort Cool Jaccard Index Mersene Twister Power Iteration Swarm Ray tracing Intelligence A Search Fractal Gaussian Compression Elimination Bogosort Beam Search Hash Function Fine HeaD's Permutation freneraton Laplacian Smoothing BreadthDepth First Search Binary Search Back- propagation Backtracking Fast Fourier Cross-Entropy Transform Method Descriptive Boring k-means Linear Interpolation Mergesort Nearest Neighbour Proof-of- Work PageRank Secure Hash Truncated Binary Algorithm Exponential Backon Topological Sort Quicksort Trying Too Hard Algorithm X Demon Algorithm Doomsday Algorithm Too Sure of General Problem Itself Solver Bellman- Fisher-Yates Boyer-Moore Bayesian Cocke-Younger- Djikstra's Ford Shuffle String-Search Something Kasami Algorithm Just Some Dudes Diffie- Hellman Floyd- Warshall Gomory-Hu Lempel-Ziv Huffman coding Hamming Distance Knuth-Morris- Pratt Lloyd's Algorithm Rivest-Shamir- Adleman Trash Dynamic Programming ProdrammerHumor.io TiERmAkER

Content BEAUTIFUL PIECE WHAT WAS YOUR INSPIRATION? I FORGOT THE STOP CONDITION

NixOS/nixpkgs has 58,000+ issues in their GitHub repo, and finding anything in there is like searching for a specific grain of sand on a beach. The naming conventions are so cryptic that even if your issue exists somewhere in that digital haystack, good luck finding it before the heat death of the universe. The genius here is that the repo has achieved immunity to duplicate issue closures through sheer volume and terrible searchability. Your issue about some obscure package build failure? Sure, it probably exists already, but buried under 57,999 other issues with titles like "build fails" or "error in configuration.nix". The moderators can't close your issue as a duplicate if they can't find the original either. It's defensive programming applied to issue tracking. Fun fact: nixpkgs is one of the largest repositories on GitHub by commit count and has more packages than the Arch User Repository. Managing that many issues is basically a full-time archaeological expedition.