Learning Linux: Theory vs. Catastrophic Practice

Content RUN C:S Type a simple command into the console Press up key dozens of times until you find it.

Content ALL MODERN DIGITAL INFRASTRUCTURE A PROJECT SOME RANDOM PERSON IN NEBRASKA HAS BEEN THANKLESSLY MAINTAINING SINCE 2003 A random nerd in Ohio who can feel millisecond delays

Content 5 Answers Active Oldest Vo You can bind the 'input' event to the textbox. This would fire every time the input changes, so when you paste something (even with right click), delete and type anything. 790 ('myTextbox").on ('input', function() do something ); If you use the change handler, this will only fire after the user deselects the input box, which may not be what you want. There is an example of both here: http:jsfiddle.net6bSX6 Share Improve this answer Follow answered Oct 9 '12 at 10:21 Timm 11.9k 4 0 30 42 197 This does not work in the Nintendo 3DS browser. The change is not detected even though the input field contains the new string. - Johan Jul 3 '13 at 11:30

Content Hacker Scripts 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 I'm keeping those

The duality of forced shutdowns! Physically, it's just a simple power button press. Emotionally? You're basically Boromir dying in Aragorn's arms after slaying your unsaved work and 47 browser tabs. That moment when you hold down the power button feels like executing Order 66 on your digital empire. "I'm sorry little one, but these 8 hours of compiling must die because Windows Update decided today was the day." The ultimate digital mercy killing that somehow feels like a war crime.

Content Clients: There are some corner case bugs in your software, why don't you code in such a way there aren't any bugs. Me: yuva.krishna.memes My goodness, what an idea. Why didn't I think of that?