Kicking off IMSBD Weekend Early
11-28-2017, 04:05 PM
#63
11-28-2017, 04:17 PM
#66
Oh and I know there is no way ettil has standards given that she married me 
Can you even begin to comprehend what living with me for 23.5 years must be like?
She did get a 911 out of the deal though. A 996, but still...
Can you even begin to comprehend what living with me for 23.5 years must be like?
She did get a 911 out of the deal though. A 996, but still...
11-28-2017, 05:00 PM
#68
If any of you know the meaning of Python, Django, ROA, and/or Infoblox, I pity you. Unless you are the jackass that wrote the code I'm working on. Then being the tail of the human centipede is too good for you!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
11-28-2017, 05:04 PM
#70
Rennlist Member
If any of you know the meaning of Python, Django, ROA, and/or Infoblox, I pity you. Unless you are the jackass that wrote the code I'm working on. Then being the tail of the human centipede is too good for you!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
11-28-2017, 07:32 PM
#72
Rat Balls
Rennlist Member
Rennlist Member
Join Date: Dec 2011
Location: Scottsdale AZ, USA
Posts: 3,636
Likes: 0
Received 13 Likes
on
13 Posts
How f'ing long does it take Mark in Baltimore or Pirate Guy to figure out what went on in the GWIT996F?
I'm sure Gretch would have just called KK a name and let things progress nicely....
I'm sure Gretch would have just called KK a name and let things progress nicely....
11-28-2017, 08:05 PM
#73
Race Director
Thread Starter
If any of you know the meaning of Python, Django, ROA, and/or Infoblox, I pity you. Unless you are the jackass that wrote the code I'm working on. Then being the tail of the human centipede is too good for you!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
If you don't know what those words mean, then you should feel blessed and simply punch anyone that tries to bring them into your life in the face!
My faves are the ones that explain in great detail the incredibly important include files but don't actually list the names of the sh*t actually IN those files. What I'd LOVE to do is actually instantiate some of that code without a week-long research project. Instead, you just keep opening and reading successive layers of included tripe - like somehow if they hid the REALLY sh*t code seven includes deep, nobody would find it? - all the while discovering that the comments get less and less frequent and less useful, like the chalk line you stop caring about after you've been in the cave for three days and the flashlight's long dead.
I've been angry at many people; I've road-raged. I've done the old-school-pick-the-other-guy-up-by-the-lapels-and-slide-up-a-wall. Once, I regained my senses from the red mist and noticed that I had another guy pinned against the wall with my forearm across his throat and my right fist in the firing position, poised to make it so the wide-eyed dude craps his teeth back out in 2 days. But none of those compare to trying to de-obfuscate some terrible design because your lousy predecessor (or worse! some hired hack or offshore "resource") had some stupid first-year OOP instructor who had a hard-on for nested included libraries.
Also, to those Python people who say "Oh, the indenting is really useful once you get used to it," I hope you get hit by a train.
11-28-2017, 09:03 PM
#74
Here's the million-dollar question: too many comments, too few comments, or utterly worthless comments?
My faves are the ones that explain in great detail the incredibly important include files but don't actually list the names of the sh*t actually IN those files. What I'd LOVE to do is actually instantiate some of that code without a week-long research project. Instead, you just keep opening and reading successive layers of included tripe - like somehow if they hid the REALLY sh*t code seven includes deep, nobody would find it? - all the while discovering that the comments get less and less frequent and less useful, like the chalk line you stop caring about after you've been in the cave for three days and the flashlight's long dead.
I've been angry at many people; I've road-raged. I've done the old-school-pick-the-other-guy-up-by-the-lapels-and-slide-up-a-wall. Once, I regained my senses from the red mist and noticed that I had another guy pinned against the wall with my forearm across his throat and my right fist in the firing position, poised to make it so the wide-eyed dude craps his teeth back out in 2 days. But none of those compare to trying to de-obfuscate some terrible design because your lousy predecessor (or worse! some hired hack or offshore "resource") had some stupid first-year OOP instructor who had a hard-on for nested included libraries.
Also, to those Python people who say "Oh, the indenting is really useful once you get used to it," I hope you get hit by a train.
My faves are the ones that explain in great detail the incredibly important include files but don't actually list the names of the sh*t actually IN those files. What I'd LOVE to do is actually instantiate some of that code without a week-long research project. Instead, you just keep opening and reading successive layers of included tripe - like somehow if they hid the REALLY sh*t code seven includes deep, nobody would find it? - all the while discovering that the comments get less and less frequent and less useful, like the chalk line you stop caring about after you've been in the cave for three days and the flashlight's long dead.
I've been angry at many people; I've road-raged. I've done the old-school-pick-the-other-guy-up-by-the-lapels-and-slide-up-a-wall. Once, I regained my senses from the red mist and noticed that I had another guy pinned against the wall with my forearm across his throat and my right fist in the firing position, poised to make it so the wide-eyed dude craps his teeth back out in 2 days. But none of those compare to trying to de-obfuscate some terrible design because your lousy predecessor (or worse! some hired hack or offshore "resource") had some stupid first-year OOP instructor who had a hard-on for nested included libraries.
Also, to those Python people who say "Oh, the indenting is really useful once you get used to it," I hope you get hit by a train.
Seriously. They SUCK! I horked all of Prod a few months ago because I had the audacity to (accidentally) run 8 (yes, 8) simultaneous actions against Infoblox and it brought the whole grid down to the point that we couldn't get in and reboot it. Support's response? Don't send so many requests
And yeah fvck Python and it's white space