argus

As in, “aye, meh boy, ah been bernin’ eet”. Tonight marks a first for me: an all-nighter at work. As in not going home from the day before.

Off the bat I can think of a few negatives: obviously, you’re wiped out. But others: same clothes (Do they stink? No… Will people notice? Do I really care?), scarcity of food (Papa Johns across the street, 24 hour Ga Tech Kroger, the at-work snack store that I run… hooRAH), an exponentially deteriorating appearance (stubble, greasy skin, greasy-nappy hair, possibility of bags under eyes, etc.).

(more…)

To hear some of the guys in my division tell it, that was the final score from the intralab division-versus-division softball showdown at our annual Electronic Systems (ELSYS) lab picnic.

Yes, I’m posting pictures from work. Here.

Here at work, we write code in a programming language called Python. Since there is more than one person writing code in this language, we have a standard of conventions to follow — things like “always put a space after a comma in a list of function variables”, etc.

Well, one of the more asinine standards (which means “things that you have to do to write correct code” according to my project manager) that we have adopted is maximum line length. If you are writing some code and the line exceeds 78 characters, then you have to reformat that line to break into two lines.

This has some advantages — namely that the code is printable without unexpected formatting behavior — but also is a colossal pain to remember to do, and ends up making a longer-than-average-but still-elegant line look nasty and choppy. IMO.

Things like this should be guidelines, not standards.

<breath> OK. Done :)