Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share It With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

ADVERTISEMENT
ADVERTISEMENT

Links 1 through 10 of 29 by Drew Thaler tagged programming+humor

No, it's completely wrong-headed, insane and unreasonable. Your code is 100% bogus and should be taken out the back, lined up against a wall, and machine-gunned.

Then the bleeding corpse should be hung, drawn and quartered.

Then burnt.

Then the smouldering rubble should be jumped up and down on.

By a hippo.

Share It With Others!

So, as a public service, I’m going to list assumptions your systems probably make about names. All of these assumptions are wrong. Try to make less of them next time you write a system which touches names.

Share It With Others!

I explained as politely as I could that separation of concerns is one of the most fundamental of all the principles of system design, and that for me to reschedule my own tasks and take on other agents’ responsibilities would be a gross violation of encapsulation. I explained that, instead, when she accepted the get-the-boys’-drinks interrupt, she should have relinquished her lock and passed the cheese back down to my end of the table before going swanning off off on the drinks mission.

Sadly, she was COMPLETELY IRRATIONAL and started talking as though I was some kind of selfish jerk who just wanted the cheese.

I tried to be sympathetic, but the bottom line is that she was wasting a valuable opportunity to BENEFIT FROM MY EXPERTISE and learn important architectural principles. I just don’t understand women.

Share It With Others!

To remove the confusion over the distinction between the NULL constant, the “0” constant (for pointers), and C++0x’s nullptr constant, and to increase type safety, the null constant is now a template:
MyClass *ptr = std::pointer_constants<MyClass *>::null();

Share It With Others!

There has been a long running debate in the Application Platform Services Group here at Burton Group between the REST people on one side and the SOAP people on the other. For the most part it mirrors the external debate. In one recent exchange, while discussing the complexity of SOAP and the web services framework, the SOAP side said, “Before all of the WS-* stuff, SOAP was actually simple. That’s what the ‘S’ stood for.”

Share It With Others!

Share It With Others!

1973's revenge. "And that is why, in 2009, when developing in Microsoft .NET 3.5 for ASP.NET MVC 1.0 on a Windows 7 system, you cannot include /com\d(\..*)?, /lpt\d(\..*)?, /con(\..*)?, /aux(\..*)?, /prn(\..*)?, or /nul(\..*)? in any of your routes."

Share It With Others!

Heh, funny on so many different levels: Hyper-sensitivity. Developer's quick 'n dirty response - strip the headers and no more problem, right? Then of all the possibilities, the one created on a Mac was actually selected to be the public face of Ubuntu. (Which in turn somewhat justifies the hyper-sensitivity...)

Share It With Others!

Notice that as $ approaches zero, Stupidity goes to infinity.

Share It With Others!

Super-old-school errors. This list looks like it was compiled from Usenet posts circa 1991 and earlier.

Share It With Others!

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT