This morning I feel like I'm literally going insane.
It seems perfectly rational for me to look at *anything* in the 'normal' world and consider it as completely, entirely, and utterly insane.
Other people might not be insane 'according to them'. Other people are worse than me though. Not only are they freaking insane, they're too stupid to know it.
Today though, I really do just want to run screaming naked onto the street jump on the first car I see and piss on its windshield.
It's Visual Studio that's doing it. I'm sure I could handle the world's insanity, but VS.NETs apparent slowness today feels like it might be the straw that breaks the camel's back.
I'll look to Fat Boy Slim for solace.
Words fail me.
What's so slow in VS.NET?
I'm using it everyday and I still don't have to cope with such symptoms...
I've been restructuring folder structures, namespaces, etc. I have 38,785 files in 3,750 folders presently in my 'project' folder.
I'm trying to bash them into conformance with my will.
The thing that's really killing me is this incessent lag. I have a wireless mouse, that goes through a KVM that goes through terminal services that connects to the computer that has my email client on it. Technically, it's fast. But it's got that 'little lag' that's slowly driving me insane.
Also, I have three monitors, and this new wireless mouse has terrible resolution. I'm not sure if it's because of flat batteries or what... but I have to use the mouse. I can't just put it on the charger when I need to use it. Anyway, when I move my mouse the smallest movement I can make it do is like 4 or 5 pixels. Which sucks. I've decided that's the cause of my real frustrations.
The VS.NET stuff it it trying to load a few hundred thousand lines of code, and connect to web projects that aren't there, and shit like that...
It'll all be better soon I'm sure.
Fucking hell!!
I just switched mouses, and now when I single click the fucking computer conducts a double click.
I'm gonna go for a walk.
I have had that problem once... I had 2 wireless adapters and they both were catching signal from the same mouse.