The Current Job Market Nowadays

Ah, the classic "let me check every possible capitalization pattern" approach! This developer is manually checking for true , True , TRue , TRUe and then the same for false variants instead of just using toLowerCase() once and comparing to a standard value. The function even returns maybe if neither pattern matches, which is both hilarious and terrifying for Boolean logic. Somewhere, a computer science professor is feeling a disturbance in the force. This is the kind of code that makes code reviewers develop eye twitches and start muttering "string.toLowerCase() === 'true'" in their sleep.

Content ralfmaximus Years ago back when I worked in cubicle land, we were hiring junior software developers. They didn't have to have a ton of experience, just a willingness to learn, and some demonstration of their software skills. Like: show me a program you wrote (any language) or a web site you designed. Anything. And there was this one guy I talked with who seemed super sharp, but had virtually zero experience writing software. When it came time to do the show-n-tell part of the interview he whips out his laptop, brings up a website, and spins it around to show me what he made. A website of tiny ceramic frogs. Not for sale. Just... all these ceramic frogs, organized into categories. Frogs on bicycles, frogs with hats, frogs sitting on lily pads. It was a virtual museum of ceramic frogs in web form. I scrolled through his online collection of frogs, slightly baffled. "This is your website?" I asked finally. "Yep!" "You coded this yourself?" popped into view-source mode and poked around some incredibly well-formatted, well-commented html. I nodded slowly. This guy was meticulous. "Yep!" "So... where'd all the frogs come from?" "I made those too," he says, beaming. And while I'm processing this he rummages in his bag and pulls out a little ceramic frog working at a computer terminal. He places it on the table before us, next to the laptop. "And THIS one," he says, "I made for you! As a thank you for the interview." It was adorable. I hired him on the spot. I mean, why not? Worst case he'd wash out in 90 days and we'd hire somebody else. He turned out to be one of the best developers on our team. And yes, his cubicle was loaded with ceramic frogs. magical-awesome-kid This is absolutely adorable and I want this man developing all of my websites. 16,939 notes O

Content boot brokeovariable a truer steing(? brokenstrings After all, why not? Fboot brokenVoriable true: string) brokenstrings - new stringt"Aaaan", "Goddann It", "None of this works"); foreach(string brokenString in brokenStrings) if (brokenString.Length 3) brokenVariable a false: AlEA 115 154686 Why shouldn't I keep it? ProdrammerHumor in

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), 44 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 eqnarray envir in shortstack, 1' interword space, 14, before or after hs in math mode, 51 produced by invisil too much with Isl without line break, intextsep, 200 intraword dash, 14, 11 invalid character errot invisible character, 12, 32 command, 169 delimiter, 47 environment, 169 term made with Imb text, 82, 97 iota (4), 41 isodd, 196 italic type shape, 16, 3; in math mode, 51, 15 used for emphasis, 17 Jitem, 24-25, 34, 184

Content GENTLEMEN, IT IS WITH GREAT PLEASURE TO INFORM YOU THAT I GOT MY FIRST SOFTWARE DEV OFFER

Content Being the only one capable of fixing a bug in production that caused it