Cache All Things

Content GMU Fall 2022 - CS 211 - Exercise 3 This exercise is worth 5 of your total grade (instead of 3) Additionally, there is an optional task for 1 extra credit Due Date: Friday, December 2nd, 11:59pm Changelog Copy Select All Look Up Description The purpose of this assignment is to practice iterators and inner classes in Java and, optionally, graphical user interfaces too. The theme of this assignment is the detection of fake reviews on a popular website called RateMyTeacher which allows anyone to post anonymous ratings of any teacher they want without authenticating themselves. Your task is to write "smart" iterators that are able to traverse list of reviews by skipping any words or posts that are considered fake There are mainly two approaches in implementing an iterator in Java. One is using a separate class that implements the Iterator interface and the other one is implementing the Iterator interface as an anonymous inner class. You're going to practice both approaches by writing two different iterators. Additionally, you can optionally implement a GUI to make your application more user-friendly and get some extra credit. Instructions Honor Code: This assignment is individual work of each student, you're not allowed to collaborate in any form. Copying code from other sources (peers, websites, etc.) is a serious violation of the University's Honor Code. Your code will be examined for similarities with other sources. Validation: Make sure all method parameters are properly validated (e.g. String args can't be empty, etc.) Documentation: Comments in JavaDoc-style are required. You must comment each class, each method and each instanceclass variable you declare. You must also comment any piece of code that is not obvious what it does. Visibility: All fields should be made private. All methods provided in the specification are public. You may add any fields or methods you want as long as they are private. Packages: You may not import any classes except Scanner, File, ArrayList, Iterator ProarammerHumor.io

Content Based on a true story: xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that. xxx: So we're sitting here, looking through his, uhm, "legacy" xxx: You're gonna love this xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login. xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help" "trouble" "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time". xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling wellgonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am. xxx: (and the oscar goes to) fucking-coffee.sh - this one waits exactly 17 seconds (!), then opens a telnet session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has a TCP socket up and running) and sends something like sys brew . Turns out this thing starts brewing a mid-sized half- caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk. xxx: holy sht l'm keeping those

Content rpics uhackergirl888 10h i.redd.it 53 1 52 15 20 3 18 8 11 Landlords- please don't paint over cockroaches. ArtsCrafts Join IMixStuff 10h E 21 Awards Its not a bug, its a feature. 4 Reply 4 11.2k J

The evolution of a programmer's hairline perfectly correlates with their tech stack choices. Start in UI/UX with a full head of hair and optimistic dreams. By the time you're doing Frontend, you've seen enough CSS bugs to lose a bit. Full Stack JS and Mobile devs? That's when the real receding begins. C#/Java programmers have accepted their fate along with their verbose syntax. DBAs are too busy optimizing queries to notice their optimization problems up top. But DevOps/SysAdmin? Those 3AM production failures have claimed most of the hair. And if you've reached Embedded programming, congratulations! You've traded your hairline for the ability to make a microcontroller blink with only 12 bytes of memory.

The first rule of game development: always sanitize your inputs . Some poor dev just learned that VARCHAR(255) isn't enough when players can create display names like "ConundrumSupercalifragilisticexpusVortexWhimsicalWhisperXenodochialXyloglyphyYesteryearYggdrasilZanyZephyrZigguratZillionaireZenithZealotZiplineZigzaggingZephyrine" while flying spaceships and making terrible tuna puns. The database admin is probably having a nervous breakdown right now while the QA team is laughing hysterically. And somewhere, a junior dev is frantically writing a regex at 2 AM that they'll eventually copy-paste from Stack Overflow anyway.

Sweet summer child! Frontend devs looking at e-commerce like it's just a fancy contact form with extra steps! 😱 Meanwhile, backend devs are SCREAMING into the void about payment gateways, inventory management, tax calculations, and shipping logistics! That beautiful butterfly represents the HELLSCAPE of user sessions, cart abandonment, and regional pricing that's about to DEMOLISH their naive little frontend souls. Honey, an e-shop isn't just a "complicated form" - it's where simplicity goes to DIE and developer tears flow like champagne at a tech billionaire's divorce party! 💀