PC Case For Hamsters, EZ Bake Oven in a Drive Bay
ResQuad noted that Slashdot's OSDN Sister site ThinkGeek is selling some exciting new products including a PC Case for Hamsters
and an EZ Bake Oven that fits in a 5.25 drive bay. They also have a limited run T-Shirt with a s3kr1t message on it. Lots of other fun stuff too.
This is getting boring now. These AF jokes really suck big big time. I mean cmon guys - one AF after another - are there so many morons out there?
*thinks*
Never mind.
It doesn't look like that is an ACTUAL case.
1: Why would you put a side panel on it, then have something non-flexible poke through it? Any attempt to slide off the side panel would cause the plastic tube on the front of the case to break or, slice the hamster like a guillotine.
2: The U bend at the top is right on top of where the power supply goes. That's not right.
3: How is one to access their CDROM/floppy/Zip100/insert favorite media drive here if the hamster ball on the front of the case BLOCKS ALL THREE BAYS?
4: click on 'Add to wish list ad prove my point'...
Partnership for an idiot free America!
In case you don't have a slashdot paid account..
Dating Design Patterns
Posted by timothy on Thursday April 01, @03:40PM
prostoalex writes "How many times, when playing Dungeons and Dragons by yourself, or reading an RFC in the bed alone on a Friday night, have you thought 'Boy, I sure wish there was an easier way to pick up women, like published API with code samples?' What would you say if such documentation was not only available, but succinctly put into 22 design patterns and given formal descriptions just like the ones in your UML book? Dating Design Patterns, with a cover suspiciously similar to Design Patterns by the Gang of Four, is the first attempt to bring verified solutions to common problems in the world of dating." Timothy's review follows prostoalex's, below.
Dating Design Patterns
author Solveig Haugland
pages 150
publisher Solveig Haugland
rating 9/10
reviewer Alex Moskalyuk
ISBN 0974312002
summary Elements of reusable objective-oriented paired programming
Why design patterns are needed
Many will attest that the API to the WOMEN platform is somewhat obscure, contradictory and poorly documented. However, if you talk to any randomly selected groups of men, you will discover that the problems they face (whether in Pickup or Relationship states) are fundamentally the same. If there's a common set of problems, shouldn't there be a common set of solutions? Moreover, doesn't it bother you that programming geeks, who advocate code reusability and open-sourcing have not come up with reusable successful solutions for commonly occurring problems and have not documented them?
This book is the attempt to change that and unite all design patterns in a single documentation project. You can read the conversation that led to writing DDP (caution: those of you in love with Design Patterns' concept might have a hard time reading how it was all a hoax by the Gang of Four). Hopefully you will understand the danger of letting this knowledge out (hint: geeks who talk to attractive girls, date and get laid spend less time writing code, which could jeopardize some projects) and not recommend the book to everyone you know. The table of contents is available online as well (in PDF format), and you can see that the book is subdivided into two large sections - introduction and pattern catalog.
Introduction to dating design patterns
In the first part, the authors introduce the concepts of design patterns with several superfluous definitions in an attempt to outdo the academic titles types on Design Patterns in number of formal references and quoted italic text. They also provide the set of anti-patterns, which can be collected by surveying poor implementations of dating patterns. For example, the Iterator anti-pattern is described as "The nag. One of the most taxing on system resources. Also an anti-pattern when used to repeatedly ask the same woman for a date." Many developers fall into fallacy of thinking anti-pattern would do the job when a pattern does not work.
The chapter on refactoring talks about all the issues that must be taken care of before implementing any of the patterns. Each refactoring unit includes sub-sections on Motivation, Mechanics and Example. The motivation part explains how this refactoring unit can help publish an attractive public interface for FEMALE platform. The mechanics part usually includes a bulleted list of what needs to be done for the implementation. The example brings us into more practical world, where we can visualize how the refactoring units "Get a makeover", "Display yourself in a new context through third parties", "Publish a more restricted interface" and "Fake a phone call from an ex-girlfriend" can help interested geek attract female companions.
Pattern Catalog
The second part is nothing more but a collection of 22 existing dating patterns. This part of the book will be even more familiar to those who read the original Design Patterns, as the headings, bulleted lis