the standard corporate practice of first initial, last name has yielded some funny ones too, and has even given rise (at least at places I've worked) to calling people by their logon ID rather than their name when it's easier to say (such as a fomer coworker that we simply called: "clink"). But the best was a programmer I used to work with named Dan Alcock. Obvious last name jokes aside, some others on the software staff, not liking him, began to refer to him as "d anal cock".
Well, I haven't seen a Cafitrol patch, so the best way I've seen is to step down gradually and keep tylenol around. That is how two of my friends beat the addiction. It took about 3 weeks to get off completely.
Me? I've thought about it, but I don't have the willpower *grabs bottle of Bawls*...mmm....bawls....
That's about on par with the job I saw last autumn. "5+ years.net experience (C# or VB.NET).". I sent them my resume, and a note explaining that.net had only been official for about 6 months at that time, but that I had been programming the beta for the 2 years that it had been available. The wrote back saying that I didn't have the desired.net experience....go figure.
Because BILL! said it, it must be bad.
I don't see anything wrong with the statement. Any coder on/. with any experience on even the smallest of systems knows that there is no such thing as a perfect system the first time around. We like to think in terms of OO and loosly-coupled systems don't we? Well, secure code from Microsoft is just one object of the "security model". He's absolutely right. Firewalls were invented for a reason. So was antivirus software. These are just pieces of the pie that, when coupled together with secure software, provide multiple layers of protection. No one piece of the model should be expected to do it all. And if MS can patch what it misses quickly enough, which they have been much better at of late, then it is our (the user's) job to apply those patches and keep our security system running at full capacity. I didn't have a single problem with MSBlast or any of the other latest and greatest viruses/worms. I didn't get Nimda, I didn't get Code Red, I didn't get SObig...I keep my patches up to date, I run a firewall, I have antivirus software, and I'm generally careful. I don't think that it is too much to ask of the end users to put their own houses in order, so to speak, using the tools that are readily available.
I mean come on, it isn't like he completely absolved himself (and by extension the company) of all responsibility, he just correctly recognizes the nature of the secured system.
Slashdot Mirror
the standard corporate practice of first initial, last name has yielded some funny ones too, and has even given rise (at least at places I've worked) to calling people by their logon ID rather than their name when it's easier to say (such as a fomer coworker that we simply called: "clink"). But the best was a programmer I used to work with named Dan Alcock. Obvious last name jokes aside, some others on the software staff, not liking him, began to refer to him as "d anal cock".
Well, I haven't seen a Cafitrol patch, so the best way I've seen is to step down gradually and keep tylenol around. That is how two of my friends beat the addiction. It took about 3 weeks to get off completely. Me? I've thought about it, but I don't have the willpower *grabs bottle of Bawls*...mmm....bawls....
and by cool you mean TOTALLY SWEET!
That's about on par with the job I saw last autumn. "5+ years .net experience (C# or VB.NET).". I sent them my resume, and a note explaining that .net had only been official for about 6 months at that time, but that I had been programming the beta for the 2 years that it had been available. The wrote back saying that I didn't have the desired .net experience....go figure.
Because BILL! said it, it must be bad. I don't see anything wrong with the statement. Any coder on /. with any experience on even the smallest of systems knows that there is no such thing as a perfect system the first time around. We like to think in terms of OO and loosly-coupled systems don't we? Well, secure code from Microsoft is just one object of the "security model". He's absolutely right. Firewalls were invented for a reason. So was antivirus software. These are just pieces of the pie that, when coupled together with secure software, provide multiple layers of protection. No one piece of the model should be expected to do it all. And if MS can patch what it misses quickly enough, which they have been much better at of late, then it is our (the user's) job to apply those patches and keep our security system running at full capacity. I didn't have a single problem with MSBlast or any of the other latest and greatest viruses/worms. I didn't get Nimda, I didn't get Code Red, I didn't get SObig...I keep my patches up to date, I run a firewall, I have antivirus software, and I'm generally careful. I don't think that it is too much to ask of the end users to put their own houses in order, so to speak, using the tools that are readily available.
I mean come on, it isn't like he completely absolved himself (and by extension the company) of all responsibility, he just correctly recognizes the nature of the secured system.