Proc Jokes

Q: How many SAS programmers does it take to change a light bulb?
A: One to analyze the historical failure rates of lightbulbs using PROC LIFEREG, so as to anticipate the failure of the lightbulb before the user actually has to report it, one to explain why SAS is better for changing lightbulbs than S-Plus, SPSS/X, BMDP, SYSTAT, MINITAB or a spreadsheet, one to write a custom interface in AF/SCL allowing the user to manually request the changing of the light bulb after its failure (prematurely) occurs, one to write a report with PROC SQL and PROC REPORT which will summarize the lightbulbs needing to be changed, sorted twelve different ways, cross-indexed (by wattage, type, and prematureness-of-failure) and totaled, one to actually spin the light bulb into the socket using SAS/Insight, one to call Cary to try to get them to explain when a new version of the lightbulb will ship, how much we'll pay to keep using lightbulbs for another year, and what we'll do if our site sends all its more...

Q: How many SAS programmers does it take to change a light bulb?
A: How many?

Q: How many SAS programmers does it take to change a light bulb?
A: It depends: If they are applications programmers, it takes exactly twice as many as are currently available. If they are host programmers, it takes one for each variant of Unix and/or MicroSoft Windows. If they are core programmers, it only takes one. He just holds the bulb to the socket and waits for the world to revolve around him.

Q: How many SAS programmers does it take to change a light bulb?
A: One to analyze the historical failure rates of lightbulbs using PROC LIFEREG, so as to anticipate the failure of the lightbulb before the user actually has to report it, one to explain why SAS is better for changing lightbulbs than S-Plus, SPSS/X, BMDP, SYSTAT, MINITAB or a spreadsheet, one to write a custom interface in AF/SCL allowing the user to manually request the changing of the light bulb after its more...