To Over or Under Engineer?
In which two groups of software engineers design and implement a fly-killing machine.
"The product has gone through extensive testing. During the tests, in which we mocked the size, movement pattern and speed of the common fly, the device performed with 80% efficiency", the lead engineer commented when asked by the press about the secret to their rapid development process.
"Suffice to say that we had to make some design and implementation sacrifices to cut the time to market and production costs" he commented briefly on the effectiveness of the product.
"We wanted a device to not only be effective against the common fly but be as useful in a possible case where the flies, due to possible nuclear experiments, possibly mutate and possibly grow both in size and power." the lead technical architect of the team, while showing a photo of a possible mutant fly, replied when asked why the project took so long.
He, displaying a photo of the "magnificent" design, later commented on the efficiency of the device "well, it's kind of effective against the common fly; you can be sure the fly is dead with the double barrel 155mm cannon, provided that you can aim around the fly; that is if the 3 men crew learned to correctly and swiftly maneuver the 79 tons perfect fly-killing-machine."
"At this stage, we are looking for more investors to finish the first prototype. We just need to raise another $348 million to get the ball rolling as soon as possible", he replied to a question about when the product will hit the market.
At the end of the conference, he reiterated "It is most important to remember that the owner will be perfectly ready to confront any mutant flies. Even though the probability of a mutant fly is about 1x10-23, one has to be always prepared."
Image sources: Pinterest, Devian Art, Wikia, Wikipedia
Once Upon A Time...
Two groups of software engineers, one favouring Java and another favouring Ruby, were asked to build a device that kills the common fly.![]() |
The product is supposed to kill this nasty creature. |
1 Day Later
The Ruby team announced the completion of the product."The product has gone through extensive testing. During the tests, in which we mocked the size, movement pattern and speed of the common fly, the device performed with 80% efficiency", the lead engineer commented when asked by the press about the secret to their rapid development process.
![]() |
A photo of the finished product by the Ruby team |
"Suffice to say that we had to make some design and implementation sacrifices to cut the time to market and production costs" he commented briefly on the effectiveness of the product.
367 Days Later
The Java team accomplished the design of the product."We wanted a device to not only be effective against the common fly but be as useful in a possible case where the flies, due to possible nuclear experiments, possibly mutate and possibly grow both in size and power." the lead technical architect of the team, while showing a photo of a possible mutant fly, replied when asked why the project took so long.
He, displaying a photo of the "magnificent" design, later commented on the efficiency of the device "well, it's kind of effective against the common fly; you can be sure the fly is dead with the double barrel 155mm cannon, provided that you can aim around the fly; that is if the 3 men crew learned to correctly and swiftly maneuver the 79 tons perfect fly-killing-machine."
![]() |
The "perfect fly-killing machine" as put by the Java team |
"At this stage, we are looking for more investors to finish the first prototype. We just need to raise another $348 million to get the ball rolling as soon as possible", he replied to a question about when the product will hit the market.
At the end of the conference, he reiterated "It is most important to remember that the owner will be perfectly ready to confront any mutant flies. Even though the probability of a mutant fly is about 1x10-23, one has to be always prepared."
![]() |
A possibly typical mutated fly as shown by the lead technical architect of the Java team |
Image sources: Pinterest, Devian Art, Wikia, Wikipedia
Comments
Post a Comment