Still Fits

Content Me learning programing languages Python javascript java php

Content HOW CAN YOU BE A VEGETARIAN DUDE? MEAT TASTES AWESOME BUT ANIMALS HAVE FEELINGS TOO, JEFF YEAH, EVIL ONES THOUGH I'LL BE MAPPY ONCE YOUR FAMILY IS DEAD SHOULD SELl DRUGS TO KIDS JAVASCRIPT IS THE BEST PROGRAMMING LANGUAGE

Someone's partner just discovered their search history and is questioning their entire career choice. "What is a fork," "what is a branch," "what does pipe mean"—these are literally Git and Unix fundamentals that we all Google for the 500th time because nobody actually remembers the exact difference between rebase and merge. The real kicker? "Rubberduck to talk to." Yeah, we've all been there. When the code breaks so badly that you need an inanimate object to explain your problems to. Rubber duck debugging is a legitimate technique where you explain your code line-by-line to a rubber duck (or any object really), and somehow the solution magically appears. It's basically therapy for developers, except the duck doesn't judge you for using 47 nested if statements. The stereotype says programmers are geniuses. Reality says we're just really good at Googling basic concepts repeatedly and talking to bath toys.

The beautiful irony of being a Mobile App Manual Tester who gets grief at home for being on their phone too much. Like, honey, I'm literally getting paid to swipe, tap, and break things on this device. That disappointed look you're giving me? That's just me finding edge cases in production. It's not addiction—it's professional dedication.

Content CS 4323 PROGRAMMING ASSIGNMENT 1 (SCANNER Due: March 6, 2018 This project builds the first component of a compiler, the lexical analyzer (or scanner), for TrumpScript language. The Internet explanation of the syntax of TrumpScript was incomplete, so I mixed it with other typical language features (thus the name TrumpScriptt ) and constructed context-free rules defining this modified (and simplified) TrumpScript. These rules will be further transformed later, if necessary, into the form with which LI(1) parsing can be done. A few funny features of this language include; . Every program must start with the message "Make programming great again" and end with "America is great". There is no import statement, America doesn't need it. There is no floating-point number, all numbers are integers greater than a million. There is no input statement, Trump doesn't need it Boolean values are denoted by fact and lie, meaning true and false, respectively. The language is case-insensitive. Error messages are maximally rude to programmers.

Oh the AUDACITY! You want your functions to be clean, readable, and self-documenting with proper parameter names? Well TOUGH LUCK because the dates package decided to go full minimalist mode and name everything like they're texting on a flip phone from 2003. But the MOMENT you try to feed it some actual shorthand notation, it throws a tantrum like "sorry sweetie, you're not my type" 💅 The absolute DRAMA of trying to validate dates with strict parameters while simultaneously dealing with cryptic abbreviated format strings. It's giving "I want my cake and eat it too" energy, except the cake is type safety and the eating is... well, also type safety. Choose your poison: either write "my_stinky_params" that look like a toddler named them, OR embrace the chaos of shorthand that the library won't even recognize. There is no middle ground, only suffering.