I'm Watching You

Content pzojpzoj-contest Refactor the majority of the backe.. wdotmathree requested changes wdotmathree 17d Member Assembly support is mandatory and must be added before this PR is approved. 9 156 3 kevlu8 17d Author Member Fuck you 556 275 54 kevlu8 merged commit 73aa662 into master

Content Google C vsdr Q All Videos Shopping Images News More v Search tools About 23,600,000 results (0.37 seconds) switch statement - cppreference.com - CC Reference en.cppreference.comwcplanguageswitch Jul 14, 2016 - The body of a switch statement may have an arbitrary number of case: labels, as long as the values of all constant expressions are unique switch Statement (C) - MSDN - Microsoft https:msdn.microsoft.com..kOt5wee3.as... Microsoft Developer Network The switch statement body consists of a series of case labels and an optional default label. No two constant expressions in case statements can evaluate to the Switch Case wit Chars? - C Forum - Cplusplus.com www.cplusplus.com Forum Beginners Dec 18, 2008 - 4 posts - 3 authors I don't really understand. Is inPut int, char or whatever? Basically your saying - if inPut is equal to '1', do what case 1. Ifit's equal to '2, then it C support for string in switch-case Jul 11, 2014 switch case vs if else Jun 30.2012 Switch Case Loop Mar 10.2010 switch case Oct 25. 2008 More results from www.cplusplus.com

Content So my daughter tells me you use GitHub? Yes, I upload exe to repos. You have exactly 10 seconds to get the fuck out of my house.

Everyone's having a normal day until that one developer casually SSH's into production as root. Nothing says "I choose chaos" quite like bypassing all security protocols and jumping straight into prod with admin privileges. Meanwhile, the kid who's probably responsible for this disaster is just sitting there with a smug grin, holding his juice box while the entire office has a collective heart attack. Security best practices? Never heard of 'em.

This meme perfectly captures the love-hate relationship programmers have with Rust's infamous borrow checker! The meme shows how the Rust borrow checker (the system that enforces memory safety) is perceived differently depending on your programming background: If you come from low-level languages (like C/C++), the borrow checker feels like a blessing - "Oh dear, oh dear. Gorgeous." It's preventing memory leaks and segfaults that would normally haunt you! If you come from high-level languages (like Python or JavaScript), the borrow checker seems like an unnecessary obstacle - "You f***ing donkey." Why do I need to fight with the compiler about ownership when I'm used to automatic garbage collection? It's that moment when you're trying to write a simple Rust program and the compiler keeps yelling at you about lifetimes and borrowing rules... while C++ programmers are nodding approvingly because they've dealt with much worse memory issues!

Content In case of fire 1. git commit If 2. git push F 3. leave building