Programming Is Like Writing A Book...

Content 252 indentation, paragraph, see paragraph index, 30, 74-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), 14 subscript of, 190 infinite loop, 252 infinitely stretchable length, 100, 102, 215 information, moving, 65-77, 207-209 infty (0), 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, 1' interword space, 14, before or after hs in math mode, 51 produced by invisil too much with si without line break. intextsep, 200 intraword dash, 14, 1 invalid character errot invisible character, 12, 32 command, 169 delimiter, 47 environment, 169 term made with ab text, 82, 97 iota (2), 41 isodd, 196 italic type shape, 16, 31 in math mode, 51, 14 used for emplasis, I item, 24-25, 34, 184

Content References 418 I'm a teapol Y Filter 414 URI Too Long 415 Unsupported Media Type 416 Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Content 423 Locked English (US) 418 I'm a teapot The HTTP 418 I'm a teapot client error response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffeetea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014. Some websites use this response for requests they do not wish to handle, such as automated queries. Status 418 I'm a teapot Specifications

Ah yes, the infamous "I Promise To Cleanup After The Refactor" bridge. Just like how every developer swears they'll come back and clean up their temporary hacks after shipping the feature. Five years later, that "quick fix" is now a load-bearing monstrosity that nobody dares to touch. The bridge is still standing though, so technically it works in production! And just like legacy code, it's covered in the vines of technical debt that keep growing while management insists on building new features on top. Remember folks, temporary solutions are the most permanent architectural decisions you'll ever make.

Content STOP USING FLOATS BINARY DATA WAS NOT SUPPOSED TO HAVE DECIMAL PARTS YEARS OF COMPILER DEVELOPMENT yet NO REAL-WORLD USE FOUND for anything other than char and int Wanted to use decimal numbers anyway for a laugh? We had a tool for that: It was called FIXED-POINT ARITHMETIC 'x can be FALSE', ' is a number', 'the sum of t and is 0.30000000004'-statements dreamt up by the utterly Deranged LOOK at what Floating-Point Numbers have been demanding your Respect for all this time, with all the circuits and data types we built for them (This is REAL Floating-Point Arithmetic, done by REAL computers): fld TBYTE PT rdi X2 number 0.5F; fyl2xp1 fdecstp number; fld st(0) fstp TBYTE PTR rdi i ( long ) y; fld TBYTE PR Ersil 05f3759df - ( i 1 ); fstp OWORD PTR rsp16 movsd (float ) Si; xmmO, QWORD PTR rsp16 V y (threehalfs - (2 y y ) ); ucomisd xmm1. xmmO sign exponent (8 bits) significand (23 bits) 01000100000000000000000000 0.15625 30 23 22 (bit index) "Hello, I want to know if f is a real number and less than -1 please?' 'Sure, that'll be f!f?0: -10.fff-1.f0?0:-1.ff' They have played us for absolute fools

Content 4 Next 88 I'm from Canada, but live in the States now. voles It took me a while to get used to writing boolean variables with an "Is" prefix, instead of the "Eh" suffix that Canadians use when programming. For example: MyObj.IsVisible MyObj.VisibleEh

The digital time bomb has been planted! Nothing strikes fear into a dev team like inheriting undocumented spaghetti code from someone who just rage-quit. That first day at the new company hits different when you realize you're now responsible for deciphering cryptic variable names, nested if-statements that reach the earth's core, and functions that were clearly written at 4am after a Red Bull marathon. The previous dev left behind their "masterpiece" with zero comments except maybe a passive-aggressive "good luck" somewhere. Technical debt inheritance is the gift that keeps on giving!