I've been noticing a lot of problems with Wraith lately. First, it was a bad stick of RAM, then it started turning off by itself at random. The best I could figure out was that it was a bad power supply. All the signs were there. Luckily, I had a spare power supply lying around, or so I though.
I installed the spare power supply and when I went to connect the 4-pin connector to the motherboard, it wouldn't go in. I pulled it out and looked into the connector on the motherboard, and it looked like something was stuck in there. So I looked at the connector on the old power supply. I was suprised by what I found. I've never seen anything like that before.
The best I can figure out is that it shorted out at some point in time, but it looks like it had been that way for awhile. But after thinking about it some more, the only way I could imagine it shorting where it would do that is when it was installed. I hadn't installed the power supply in that case or motherboard. I blame Duck.
So here I was, left with a dilemma. I have my old P4 2.4 GHz processor and motherboard I could install, but it has problems too. It wouldn't support the 3.2 GHz P4 from Wraith either. So I went out and spent $300 I shouldn't have. But it was either that, or work from my laptop for a long time. That's just not acceptable.
So now, I have Spectre. On the bright side, Spectre has a dual core AMD Athlon 64 x2 3800+ and 1 GB of DDR2 RAM. It's a nice speed bump.
The downside of all of it was that I had to do a fresh install of Windows Vista. I'm posting from it now, but I've still got a lot of software to reinstall today.
I've been busy lately, and I think it's starting to get to me. At the end of December, I picked up a new project, a big project.
It all started when one of my existing clients from HolosTek called me up and had an idea. He wanted to get involved in starting a dating website, but he didn't know where to start. Of course, I agreed because I'm poor and could always use some extra money.
What I didn't realize, was how big the project was actually going to be. For the last month and a half to two months, I feel like I've done nothing but work, sleep, and spend a little time with Kortnee.
I have to admit the project has been a lot more interesting than I expected. I've learned a new framework for PHP development (CakePHP) and I've learned quite a bit about using AJAX for fast page loads and clever effects. I always enjoy expanding my skill set.
The project still has a little ways to go before it's open to the public, but you can see what's available. It's called The CandiShoppe. Also, if you're interested, you can signup to be notified when the site is open. The current plans include offering totally free access to everyone on the site for the first few months. After that time, certain features will require paying a subscription fee.
Earlier today, I was finally catching up on reading Coding Horror. I've been behind on a lot of things, but that's another story. I came across an interesting artcile on BitTorrent.
The traditional method of distributing large files is to put them on a central server. Each client then downloads the file directly from the server. It's a gratifyingly simple approach, but it doesn't scale. For every download, the server consumes bandwidth equal to the size of the file. You probably don't have enough bandwidth to serve a large file to a large audience, and even if you did, your bandwidth bill would go through the roof. The larger the file, the larger the audience, the worse your bandwidth problem gets. It's a popularity tax.
With BitTorrent, you also start by placing your large file on a central server. But once the downloading begins, something magical happens: as clients download the file, they share whatever parts of the file they have with each other. Clients can opportunistically connect with any other client to obtain multiple parts of the file at once. And it scales perfectly: as file size and audience size increases, the bandwidth of the BitTorrent distribution network also increases. Your server does less and less work with each connected client. It's an elegant, egalitarian way of sharing large files with large audiences.
The part that really made me "oooh" and "aaaah" was the link to some source code for a visualization of how BitTorrent works. There's an animated gif in the article that shows part of it, but it really doesn't do the visualization justice. To remedy that, I've uploaded the java applet with the visualization so it can be seen in all it's glory.
This is getting ridiculous. Tuesday, when I came to work, my left monitor was dead. Nothing. Nada. Zilch. I had to replace it with an older monitor (which had been mine at one time) off a desk that is seldom used. It’s dark and can’t be adjusted to make it bright enough to use regularly. But it’s just usable enough to do something on.
Today, while I was talking to one of the salesmen, the right monitor died. It went fuzzy for a few seconds, then flickered, then finally went out completely. All this time, it was making odd popping sounds.
Now I have the problem of trying to steal someone else’s monitor so I can work. The LCD monitor I stole was from a not quite seldom used desk, but I can get away with it for the moment. But then I had to spend about 15 minutes getting the colors adjusted so it looked like it was supposed to. I ended up having to adjust the white point on the monitor funny to get it to be dark enough. It was just too bright.
All together, that makes three monitors that have died on me in the last 45 days. I haven’t been able to replace any of them. I’ve just had to keep stealing from where I could. This should finally force the issue so I can get replacements.
I wrote a quick program today to filter a list of email addresses out of an old email that had been forwarded a couple times. The program itself is very simple, but it took me about 15 minutes. Most of that time was digging up the proper commands for reading in the input.
I think it's mostly because I haven't written any new Perl code in about 2 years. I need to find an excuse to write more Perl so I'm not so rusty when I need.
#!/usr/bin/perl use IO::Handle; open (INPUT, ") { chomp $email; $email =~ s/^ *?>> +?(.+?),.*$/$1/; print "$email; "; } close (INPUT);
I came across this the other day and couldn't resist the urge to pass it along. The advice given won't work for long, but for short encounters, I see a high probability of success.
From Penguin Pete's Blog:
Yes, it's come to this. The same people you raked on in high school now run the world and control every gizmo you own or want to own. And, as you hold your "normal" identity throughout your life, there are times when it may be advantageous to pose as a geek. Maybe to convince your first date that you have job prospects beyond "Walmart clerk". Maybe to slip in the door at Comdex. Perhaps even to escape being hacked to death by the evil-looking punks at the Internet cafe, the ones with the Tux penguin tattoos and the Mohawks who are eying your laptop. Hint: They don't like you because of the suit and tie; they HATE that!
Well, fear not, hopeless lamer, I, a certified geek, will give you a rundown of how to pass as a geek for brief moments. Understand, these tactics will in no way work over the long term, like, say, a marriage. But in quick social exchanges, or to bamboozle your cow-orker, these tricks should work sufficiently to help you fool the rest of us into thinking that you're one of us:
One of the chief attributes of geeks, and intellectuals in general, is attitude. No, attitude doesn't MAKE you a geek, but that's not the point of this article. The point here is to FAKE it. And to fake it, you have to feign interests and opinions, and then be smugly confident that your "choices" are superior to the mainstream's.
From BusinessPundit.com's How to Network: For Introverts.
I have a problem. I'm an introvert. I'm not shy. I'm not afraid of being in public. But I am horrible at chit-chat and gossip. If I spend an evening at a social function with people I don't know or don't like, I get home and feel like I've spent all day at the ocean. It's that fighting-the-waves and drained-by-the-sun kind of tired. I would rather spend four hours with my head stapled to the carpet. I would be more comfortable that way.
The article has some good advice for those of us that have trouble in social situations. Definitely worth a read if you, like me, are indeed an introvert.
I was playing with The Funniest, which is a great way to waste some time, and I came across this image from XKCD. It gives me bad ideas.




