The Inverse Law Of Debugging Inspiration

Content When you get assigned a bug "Cannot reproduce on machine" 001

Content G Closed miku-chan03 opened this issue on 18 Oct 2017 2 comments miku-chan03 commented on 18 Oct 2017 Contributor Hii- I fixie wixied the JSON-api fucksy wucksie!!! xp I repwaced the Prototypes. func wiff a more -streamylined- kawaii Pwototypiee. funkywunks object that make the JS go sooper dooper fast!! D starts twerking Can u pwease merge my pwull wequest senpai?!! UwU gaearon commented on 19 Oct 2017 Contributor what in the name of fuck a gaearon closed this permanently on 19 Oct 2017

Content Virgin API Consumer JSON Fears HTML Limited to the what the API can do Has to identify himself even for read-only APIs API Provider takes away his endpoint 429 Too Many Requests data is 10 minutes behind Has to worry about quota Thinks that he is making his life easier begs his users for auth API keys has to verify his email, phone, driver's license, ssn, dna sample has to agree to Terms of Service and follow the the rules Tokens Chad third-party scraper follows no rules, doesn't agree to any terms of service 1 Luminati Business prozy networ scrapes so fast the backend crashes POP3 Se has no limitations can access any data he wants entire industries are dedicated to stopping him website thinks his user agent is a phone Doesn't care about changes in policies Even Javascript can't stop him pays laborers to solve captchas doesn't even have a phone number Reguests- TAI can work anonymously parses HTML with regex MULLVAD SMSPVA 2Captcha his business is profitable Can do whatever he wants millions of engineer hours, still can't stop him from scraping promising career at high-frequency trading firm (just scrapes in his spare time

The eternal wisdom of programming: even terrible documentation feels like a gift when you've spent hours staring at undocumented code wondering why the hell it works at all. Nothing quite matches that specific joy of finding a single cryptic comment after debugging for 3 hours. "// Don't touch this or everything breaks" - ah yes, the pinnacle of technical writing. And yet, we all know that one codebase with documentation so pristine it practically whispers sweet nothings in your ear. A rare and beautiful creature indeed.

Content Python Easy to learn Only one engine Requires good environment CH Ugly but fast Lots of maintanance Leaking problems Spectacular crashes JavaScript Can start anywhere Does weird stuff when carelessly controlled Java Ugly but gets shit done Detailed recording of any crash Scala Requires knowledge of advanced math Bleeding edge technology Needs to be ontop of Java to actually get anywhere

Content Me making the commit and pushing it before my colleagues, so I don't have to deal with merge errors H