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 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 lightbulbs to Europe where 120V/60Hz lightbulbs tend to explode upon insertion in 220V/50Hz circuits, one to write an incomprehensible ten line SAS macro program which will perpetually insert new filaments into all mission critical lightbulbs until its author is fired, at which point the SAS macro will automatically encode itself into a copy of the latest SAS/ETS usage notes, one to write a graphical front end to the lightbulb changing process using SAS/EIS, with little speedometers showing the number of lightbulbs changed per hour, so that management can understand why we need to buy bigger lightbulbs, one to prepare a SUGI paper summarizing the entire lightbulb project, taking credit for the design and execution of the lightbulb project itself as well as the invention of the light bulb itself, another one to prepare a second SUGI paper benchmarking lightbulb replacement on twelve different types of light sockets, with separate graphs for florescent and incandescent bulbs (made with SAS/Graph, except for the titling, axes, color, polylines, and background, which were all added manually with Cricket Graph on a Mac), ten to push the dollie loaded with SAS/Lightbulb manuals, *and*, One more to ask SAS-L for help when you really need to change that bulb, NOW.
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 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 lightbulbs to Europe where 120V/60Hz lightbulbs tend to explode upon insertion in 220V/50Hz circuits, one to write an incomprehensible ten line SAS macro program which will perpetually insert new filaments into all mission critical lightbulbs until its author is fired, at which point the SAS macro will automatically encode itself into a copy of the latest SAS/ETS usage notes, one to write a graphical front end to the lightbulb changing process using SAS/EIS, with little speedometers showing the number of lightbulbs changed per hour, so that management can understand why we need to buy bigger lightbulbs, one to prepare a SUGI paper summarizing the entire lightbulb project, taking credit for the design and execution of the lightbulb project itself as well as the invention of the light bulb itself, another one to prepare a second SUGI paper benchmarking lightbulb replacement on twelve different types of light sockets, with separate graphs for florescent and incandescent bulbs (made with SAS/Graph, except for the titling, axes, color, polylines, and background, which were all added manually with Cricket Graph on a Mac), ten to push the dollie loaded with SAS/Lightbulb manuals, *and*, One more to ask SAS-L for help when you really need to change that bulb, NOW.
Comments
Post a Comment