Senate Democrats say F U to votersFollow

Well they like most of the components--aside from vast opposition to individual mandate; they just don't like the brand name.

So, they're in favor of health care reform of some sort as long as it isn't forced down their throats by a big, bloated, inefficient government bureaucracy? Sounds like they're not in favor of the plan as enacted to me. That must make me right and you reaching. F'uck off.

So you're saying that the GOP leadership was worse than obamanomics?

No, because the GOP put several unelectable candidates on the ballot. Reid had some of the worst approval ratings in the country and beat Angle. O'Donnell was simply a joke whereas Castle would have almost certainly beat Coons. That would have been 50/50 right there. Add in McMahon who was put in purely because she could self-finance and there's your loss.

The fact that no one was predicting a GOP take-over was because of the ridiculous candidates you refused to admit were ridiculous, not because it was never in play.

I happen to think you're sniffing around the outside of a point, which is rare for you, but you're an inarticulate son of a ***** who can't wrap your fingers around a salient argument to save your life and as a result come off as a f'ucking ******. "varus you're stupid" isn't the best anyone can come up with, it just fits.

In Varusland, idiocy is a sign of enlightenment, and none glow brighter than Varus himself!

I'm reminded of the time Shadowrelm compared himself to Shakespeare & e.e. cummings.

What is a **** ant? I am intrigued.

WTF? How did a relatively uncaring "what's this?" question equate to me getting some hot **** sex? Seriously. A coworker's family member died yesterday right as some serious bugs in some production code he'd written became painfully apparent. As the only person somewhat familiar with what said code is supposed to do, I got to fix the bugs. But never fear! I've got said nifty thingie changing to the right colors and putting the right text in the right boxes when it's supposed to, and actually kinda doing the right thing. Of course, in order to support said fixes, I had to re-write sections of two other scripts I'd written (this is really more "rolling into production" code), so it was a busy afternoon.


And today, I discovered that some quick patch I'd written like 5 years ago finally ran into a situation in which it created a false test and ran some new beta software version off into the land of not-workingness. I'd long since written a more elegant way of parsing software versions for this tool, but had never gone back and applied it to that one line (mostly cause it had never broke anything until today), so not a disaster, but still "fun".


So yeah. I'm kinda like superman, even without the **** sex. Um... what were we talking about?


Oh. And for those vaguely interested, the "ugly" bit kinda didn't have anything to do with what I was directly working on. It just made the code ridiculously difficult to follow. The guy has a strange concept of "code base". He tends to write subroutines for doing various things for a number of similar programs, and then just copies and pastes them all into anything he writes so that they'll all be there (yeah. I'm boggled by that too!). Sadly, since he incorporated this after writing a half dozen very similar things, there's literally 2 or 3 slightly differently named routines which do slightly different things (or the same thing but in multiple places). And I don't mean that there's just a few duplicates. I mean that about 50 routines are each duplicated a couple times, each with slightly different logic to them. And good luck guessing which one is actually being called by the code you're trying to debug. It's pretty funny actually, when you aren't tearing your hair out.


And the arrays. He starts with a couple of files with some fields in them, each representing a piece of hardware. The fields contain things like vendor, type, name, location, etc. He then explicitly parses them into an array named for specific vendors and types and locations in order to present changing menu options to the customer. Of course, this means that he has to change his code anytime new meta data is introduced into the source files. Completely unnecessarily, since he could just pump them into generic arrays as needed, or just dump the whole thing into a hash and use that. Or... well... any of a number of better and more portable and scalable solutions.


I'd rewrite it from scratch, but my brain might just explode...

This assumes that poor and working class people agree with you that entitlements and handouts are actually in their best interest. It's a bit more complex than simply saying that he who provides the best goodies to the most people wins.