What Was That

Content 252 indentation, paragraph, see paragraph index, 30, 71-76, 150-154, 211-212 index, 74, 212 curly brace in argument, 75 idx file entry written by, 208 in command argument, 153 space around, 169 special character in argument, 75 too many on page, 143 indexentry, 75, 212 on idx file, 208 indexspace, 75 indicator, error, 29, 134 inf (inf), 44 subscript of. 190 infinite loop, 252 infinitely stretchable length, 100, 102, 215 information, moving, 65-77, 207-209 infty (co), 43 ink, rectangular blob of, 106 inproceedings bibliography entry type, 161 input character, 32 file, 12 interrow space in array or tabul 169, 207 in egnarray envir in shortstack, I' interword space, 14, before or after he in math mode, 51 produced by invisi too much with Isl without line break, intextsep, 200 intraword dash, 14, 1' invalid character erros invisible character, 12, 32 command. 169 delimiter, 47 environment, 169 term made with lab text, 82. 97 iota (1), 41 Visodd, 196 italic type shape, 16, 3 in math mode, 51, 1! used for emphasis, It Vitem. 24-25, 34, 184

When your colleague gets to use the fancy for loop with a clear exit condition, but you're stuck with the while loop that never seems to end - just like this press conference. The guy on the left is basically all of us waiting for that condition to finally evaluate to false so we can go home. Meanwhile, management keeps adding microphones like they're adding requirements to the sprint.

The purest form of programming education right here. First comes the euphoric high of getting your code to work - that burst of dopamine that feels like you've just conquered Mount Everest in flip-flops. Then, inevitably, the crushing despair when it mysteriously breaks five minutes later for absolutely no logical reason. The kid just speedran the entire emotional cycle of a 20-year programming career in about 15 minutes. Welcome to the club, kid! The only difference between junior and senior devs is that seniors know both feelings are temporary... until they're not.

Content Ted Pedersen SeeTedTalk "What's your degree in?" Computer Science. "My printer isn't working." Mine either.

The eternal battle between code quality and functionality in its purest form! The senior developer (naval officer) is appalled by your spaghetti code abomination, but the junior dev (Jack Sparrow) has the ultimate comeback—it might be held together with duct tape and prayers, but dammit, it compiles and runs in production! Every programmer knows that feeling when you've hacked together a solution that makes seasoned engineers question their career choices, but somehow passes all the tests. The compiler doesn't judge your methods, only your syntax!

The duality of coding confidence! On the left, the TDD practitioner smugly smiles because their tests were written before the code, so green tests actually mean something. On the right, the dark side reveals the non-TDD developer's twisted grin—sure, all tests are green, but only because they wrote tests that validate whatever garbage they already implemented. It's like measuring your height with a ruler you made yourself. "Look mom, I'm 7 feet tall!"