It is what it is.

Content Real Develoners I have to type In for every new line HTML Pseudocoders New line go br geekyornerdy

Content How to confuse machine learning:

Content def spreadsheetupdatingservice): newspreadsheetid updatespreadsheet ) with open('Assetsspreadsheetid', 'W') as f: f .write (newspreadsheetid) with open ('Assetsspreadsheetlastupdatetime', 'w') as f: f.write (datetime.now() .strfti Typo: In word 'lastupdatetime' Replace with 'masturbate' Alt Shift Enter More actions... Alt Enter Timer (3600, spreadsheetupdating. D: Des updev python TimeTableBotAssetsspreadsheetlastupdatetime spreadsheetupdatingservice() ize: 5 B Type: Text (Plain text) Modified: 15102021 21:49 def getgroupindex (event) : Created: 13102021 21:59 return Database (event .peerid) .getgroupindex Jastupdatetime masturbate

Content v Lol, HTML goes brbrbrbr brbrbrbrbrbrbrbr brbrbrbrbr Translate Tweet 2:38 PM May 30, 2020 Twitter Web App

Content My team's intern just found a critical bug by shitposting in our codebase So our summer intern (who I'm 90 sure is a professional shitposter moonlighting as a dev) just saved our entire authentication service by being, well, an absolute agent of chaos. Background: We have this legacy auth system that's been running since before TikTok existed. No one touches it. It's documented in ancient Sanskrit and COBOL comments. The last guy who understood it fully left to become a yoga instructor in Peru. Enter our intern. First week, he asks why our commit messages are so boring. Starts adding memes to his. Whatever, right? Then he begins leaving comments in the codebase like: This function is older than me and probably pays taxes TODO: Ask if this while loop has health insurance Here lies Sarah's hopes and dreams (2019-2022), killed by this recursive call The senior devs were split between horrified and amused. But here's where it gets good. He's reading through the auth code (because "the commit messages here are too normal, sus") and adds this gem: yo why this token validation looking kinda thicc though fr fr no cap this base64 decode bussin wait... hold up... this ain't bussin at all Turns out his Gen Z spider-sense wasn't just tingling for the memes. Man actually found a validation bypass that's been lurking in our code since Obama's first term. The kind of bug that makes security auditors wake up in cold sweats. The best part? His Jira ticket title: "Auth be acting mad sus rn no cap frfr (Critical Security Issue)" The worst part? We now have to explain to the CEO why "no cap frfr" appears in our Q3 security audit report. The absolute kicker? Our senior security engineer's official code review comment: "bestie... you snapped with this find ng" I can't tell if this is the peak or rock bottom of our engineering culture. But I do know our intern's getting a return offer, if only because I need to see what he'll do to our GraphQL documentation.

Content Every single Tabased startup Machine learning Some simple task