I know this is a few months old, but I got a chuckle out of this! =) Back in the day I moved from C++ to VB6, then to .NET and I've been there since. Honestly I wasn't the most excited about the changes, and I probably went through all the states of acceptance getting to know VB. It's funny how things turned out, because even though I don't use it much at all any more, I actually have fond memories of it. This code though, it's funny to look at. But I'm not sure I would call it horrible for the ways that most might in knee-jerk reaction. In plain English, it's intended to do the same thing over and over again. Listen for a a message, check if it meets a criteria "good enough to try getting what it wants", if it met the first challenge, but ultimately didn't work, try again. What I dislike about it is more the fact that it's not as explicit about exactly what it's looking for, and the fact that it's not even logging errors. The fact that it's destroying and re-creating the client in this case might be wasteful at first glance, but it's clear that whatever it's looking for is just meant to wake something else up, and it probably works as intended... For all we know if it received a malformed packet and they ignored it and tried again with the same instance of the client, the old "UNIX server in the back that nobody knows how to use any more" would catch fire and have to be hit with a hammer. =)