Wednesday, November 08, 2006

Upset About Microsoft/Novell?? Take A Pill!

Sorry to write a technical article on the Half Bad Boy Blog. I hope you can bear with me. Its just that the general reaction to this whole Microsoft/Novell agreement is so baffling that I really need to talk about it.

I'm assuming you are familiar with Open Source and Linux, the freely-available and freely-created operating system which is one of the flagship open source offerings. The community of developers and users behind open source are a particular and idealistic group, not necessarily all of the same mindset, but with some generally common goals. Among them: The idea that the rights of a person to use and even modify software should be unrestricted; the passion to create high-quality, great, useful software products; and the belief that the movement is ultimately unstoppable.

And when you think about it, it is unstoppable. Linux is truly a great operating system - secure, stable, powerful, fast, versatile, and actually quite easy to use. It is a strong competitor to Microsoft Windows - better at Windows at some things, not better at others. Yet. But there are only really two main ways for a company like Microsoft to compete with Linux - on price and on features. Since Linux is free, Microsoft cannot beat Linux on price - unless they start paying people to use Windows. And with thousands of developers around the world working on Linux for free, there is ultimately no way that Microsoft can compete on the basis of features.

The effect of open source is the commoditization of software. Interesting projects will draw more developers, leading to better software, making the project more interesting, etc. The process snowballs, and once it gets to a certain size, it is pretty much unstoppable. The licensing and intellectual property laws protecting it ensure that this is the case.

Linux is beyond this point. It is not better than Windows, yet. But there is no stopping it. Eventually the computer operating system will become a commodity, and we can thank Linux for it. Microsoft won't be able to make money there anymore.


Those of us involved in the open source movement know this. We have foreseen this for years. We understand the effect of the movement. For years people involved in open source have viewed Microsoft as the enemy, because they are the antithesis of everything the open source community stands for (with the possible exception of quality software - and some would even disclaim that exception). Those involved in open source have for years said that the movement would ultimately mean the demise of Microsoft's business models, and the death of Windows as we know it today.

Surely these people don't think they knew something that Microsoft didn't. Right? Right???


Come on, people. You had to know that Microsoft would know this. Whatever you may think of Microsoft as a company - ruthless, shady, cutthroat, etc. - you surely don't think they are stupid. They realized the same things you did, long ago. They must have figured out, long ago, that eventually they will have to adjust their business plan to align themselves with this movement. They would have to do that or die.

You would think that any step that Microsoft would take in such a direction would be a sign of a clear victory. It should be viewed as a sign that the day finally came - the day when Microsoft realized they had to figure out how to play nicely with open source in order to survive. This should be viewed as the day open source won - the day when technology works on open source's terms, not the other way around.


That is what I find baffling about the reaction to this deal. The most logical explanation for this decision, on Microsoft's part, is that they realized that they needed to do this to remain relevant. Why else would they be willing to pay Novell $348M to enter into this deal? Many so-called open source experts have said that Microsoft is doing this in order to take over Linux. Hello, people! They can't do that, because of the licensing of Linux. For so-called open source experts, you sure don't understand open source very well.


Some people were initially upset about this arrangement because they were sure it violated the GPL. They were sure of this despite the fact that both Novell and Microsoft have many experienced, paid intellectual property lawyers on staff to make very sure that no such violation existed in the agreement. Now, they are upset because they think the arrangement should be a violation, even though it apparently isn't (IANAL).
I find this pretty interesting because of prior experience I've had with people regarding the GPL. I can't recount how many times arguments I've had with people over the GPL have included them saying some variant of the phrase, "Well, that is not what the GPL is intended to mean."
If you want to play in the realm of law and intellectual property, you have to play by the rules of the game, and one of the rules of the game is that a copyright license covers exactly what it states that it covers. Intent is of no significance.


I could go on and on here, but I won't. To summarize, my point here is simply twofold:
  • This agreement should be viewed as a win for the open source movement. Novell's stated objectives are to promote and protect open source. Microsoft's stated objectives are harmony and interoperability. The most logical explanation for this is that Microsoft needed to make this move to remain competitive.
  • Any parts of this agreement that you think violate the GPL are more likely a) your incorrect assumptions based on information you don't have, or b) your misunderstanding of copyright law such that the GPL should mean what it is meant to mean, and not necessarily what it says. Frankly, you pretty much need to just shut up and deal with it. You are being pretty presumptuous to assume that you know more about law than paid corporate IP lawyers.

I'm still waiting to see an argument against this that actually holds any water. Until then, I'm willing to give the benefit of the doubt. The principle of Occam's Razor implies that the most logical explanation is likely the right one - and the most logical explanation is nothing but positive for the open source movement. Take a pill and relax.

Monday, October 02, 2006

A Trip To India

I've been meaning to blog about a trip I took to India a few months ago, and I finally decided, "Matt, just get that sucker done."

My employer sent me to Bangalore, India for a week at the start of the summer on a training engagement. Whether we should have gone is not really the subject of this blog. I know it was really expensive.

I remember the day my boss came to ask me to go. I suspected I would be asked to go, since I am the newest member of the team (and the least important). Most everyone else had already been to India before, and of those of us that hadn't, some were already booked to go to China the week prior to my trip. The ones that had already been weren't too keen on going again, and since they are more important, they could make me go instead. If you think I'm being mean to the people of India, I'm not - read on and you will understand.

Here are some of the things you have to deal with in order to take a trip to India.
  1. US Passport. Apparently, this is to convince the United States that they can let you leave. I don't quite get that. But I do know that if your employer is short-sighted enough as to not really plan well for your international voyage, it will cost somewhere around $185 to get a passport in a timely fashion (like, about 1 week).
  2. Indian Visa. This is where you try to convince India that, since the United States is convinced that they don't care whether you leave, India should be happy to take you.
  3. Shots. I had shots for diptheria, tetanus, hepatitis, polio, etc. I can't remember them all. I am still having follow-up shots. One has to ask, how is it that the Indian people seem to survive just fine, but us Westerners have to get completely medicated in order to survive? My guess is, they are tougher than we are.
  4. Medication. I had to get some anti-malarial horse pills, along with a prescription to Ambien to try to help me adjust to the time change (more on this failed experiment later).
  5. Entertainment. I bought a 30Gb Creative Zen Vision M just for the occasion - and I used it, buster.
I was starting to understand why people don't want to go to India. Then the travel began, and I really started to understand.
India is a long ways away. I know you know that, but if you've never gone that far you don't quite get it. It is so far away, in fact, that if you go any farther you are coming closer to home.

Here is how the trip to India went:
  • Fly from Salt Lake City to Cincinnati. Actually, we had the choice of Cincinnati, New York, Newark, Atlanta, etc. It doesn't really matter. This is an inconsequential portion of the trip.
  • Fly from Cincinnati (or wherever) to Charles de Gaulle Airport in Paris. Try to sleep, since it is nighttime in India, even though it is just the afternoon in Salt Lake City. Take an Ambien, wake up four hours later, and feel groggy for four more.
  • Oh, by the way - if you ever have to fly through Charles de Gaulle, DON'T. What a nightmare.
  • When you land in Paris, you are just over halfway there!
  • Fly from Paris to Bangalore. Try to stay awake since it is daytime in India. Suffer from lack of thirst. Resolve to take bottles of water in your carry-on luggage next time (and then, months later, wonder if you will be able to due to new flight regulations and the potentially explosive properties of water).
  • Land in Bangalore - and be amazed.
Truly amazed. Not repulsed. Not shocked. Amazed.

Don't get me wrong. Bangalore is not really all that much like Provo, Utah. For one thing, Bangalore has much fewer Suburbans, Excursions, and 12-passenger vans. Bangalore also has many more auto-rickshaws than Provo. Also more motorcycles - but most of them are smaller and less powerful than even my Kawasaki KX 250. Traffic is insane. Traffic laws seem to be more like guidelines or suggestions. People are everywhere, even in the middle of the night.

You may ask, is it dirty in India? Yes, it is. But it is also very beautiful. Sorry, you will have to go there to see what I mean.

We checked into Le Meridien, which is highly recommended, if you can afford around $300 per night. I hooked up my laptop and called my family via Skype. They asked why I waited so long, and I explained to them that I had just barely arrived (some 30 hours later).
I then tried to sleep. I learned the hard way that my antimalarial medication has a side effect of keeping you awake. So instead of my Ambien keeping me blissfully asleep for 8 hours, it had the effect of causing me to sleep for around 3 hours, and then I would be groggy for the remainder.

This is how most of the trip went for me. I was always tired during the day. Horrifically tired. Taking microsleeps in class, unintentionally, when I wasn't doing the training. Then nighttime would come and I would struggle to get any sleep. By Thursday I had completely given up on trying to adjust my schedule and was just trying to get sleep whenever I could.

So far the trip sounds mostly like torture. It wasn't. It was one of the most amazing experiences I have ever had. I would not trade it for anything.
The singular biggest reason for this is the people. The people of India are simply great people. I could not believe how polite, friendly, and kind they were. This was true with hotel staff, restaurant staff, people in the training sessions, taxi drivers, shop employees - they were all very helpful and polite.
Of course, some readers would say that these people were all like this because I was their customer. This is not an untrue statement. However, I have also been the customer of similar people in the United States - I've stayed at hotels, gone to restaurants, ridden in taxis, etc. Rarely do I get this kind of service here.

I also got some great mementos. I picked up some jewelry for my wife - true amber jewelry along with star sapphires - some knick-knacks for my kids, and a hand-carved sandalwood chess set for myself. I will probably never play chess with it. It is great to look at.
I'm well aware of the concept of negotiating price in India. I saw hand-tied silk rugs that I could buy for $200. I was told that they take three months for one person to create. I did not take economics in college, but I'm no idiot. I know that you can't have a business if you pay your employees more than you bring in revenue-wise. So I know that person who ties those rugs is making less than $800 a year. Considering the amount of money I make, I simply lost the heart to negotiate price. I felt I shouldn't do that when I've been given so much.

I can't explain what an awesome experience it was to go there. I will never forget it - ever. The people were amazing to meet.

And the travel is the absolute pits. I am a large man - 6'2" and about 215 pounds. Not enormous, but large. I'm not really fat either. I mean, I have some extra insulation in certain regions, but mostly I'm just broad-shouldered and big. Cramming me into coach is simply inhumane. I was shoved into a seat against the side of the plane all the way from Paris to Los Angeles on the way back. The only thing more uncomfortable than sitting there was trying to get out. I had literally no legroom - my knee was crammed up against the seat in front of me. I stayed there, getting warmer, getting smellier, starving to death because they are feeding me this crappy French food.

Being in India was an experience I will never forget. I will always be grateful for that opportunity. Travelling to and from India was also an experience I will never forget. It was torture.
Overall, my trip to India was an unforgettable experience that I will always be grateful to have had, and one I don't look forward to repeating. At least not in coach.

Tuesday, September 19, 2006

Ahoy, mateys!

Avast, ye scurvy bilge rats. Seein's how today be International Talk Like A Pirate tide, 't seem'd that 't be a good idee t' include a short entry about meself, were I be a pirate.

Me pirate name:


My pirate name is:


Dirty Sam Cash



You're the pirate everyone else wants to throw in the ocean -- not to get rid of you, you understand; just to get rid of the smell. You're musical, and you've got a certain style if not flair. You'll do just fine. Arr!

Get your own pirate name from piratequiz.com.
part of the fidius.org network


Me pirate personality:
You are The Cap'n!



Some men are born great, some achieve greatness and some slit the throats of any man that stands between them and the mantle of power. You never met a man you couldn't eviscerate. Not that mindless violence is the only avenue open to you - but why take an avenue when you have complete freeway access? You are the definitive Man of Action. You are James Bond in a blousy shirt and drawstring-fly pants. Your swash was buckled long ago and you have never been so sure of anything in your life as in your ability to bend everyone to your will. You will call anyone out and cut off their head if they show any sign of taking you on or backing down. You cannot be saddled with tedious underlings, but if one of your lieutenants shows an overly developed sense of ambition he may find more suitable accommodations in Davy Jones' locker. That is, of course, IF you notice him. You tend to be self absorbed - a weakness that may keep you from seeing enemies where they are and imagining them where they are not.




What's Yer Inner Pirate?
brought to you by The Official Talk Like A Pirate Web Site. Arrrrr!


Pirate resources:
English-to-Pirate translator

Learn your pirate name

Pirate personality test


Until next September 19 - yo ho, me hearties!

Tuesday, September 05, 2006

2006 Football Preview and Guide

Glory be, it is finally football season again. And here, just a few days late, is the Half Bad Boy 2006 Football Preview and Guide.

First, the NFL football guide. Who cares. Watch whatever you want. They are mostly a bunch of criminals and spoiled brats anyway, but at least with helmets on you can mostly avoid looking at their faces.

Okay, now that the NFL is out of the way, we can get to what we all really care about - NCAA Football. Here's some guidelines for watching NCAA Football.
  1. The SEC is the definition of football. Auburn. Arkansas. Tennessee. Florida. South Carolina. LSU. Alabama. Georgia. Ole Miss. This conference always seems to have at least one title contender. Can you just imagine trying to go undefeated in conference play in the SEC? Any SEC game is a good one.
  2. Generally avoid any PAC-10 matchup if you can help it. The PAC-10 is the most overrated conference in all of football, and watching it will cause you to erroneously think that those teams are really good. With the exception of USC, most of them are not as good as everyone seems to think (witness the recent 35-18 rout of #23 Tennessee over #9 Cal last Saturday). Exception: watching a real conference destroy a PAC-10 "opponent" is good fun.
  3. Notre Dame games are usually a good bet. With their high-profile TV contract, these guys usually draw a great opponent every week, from all across the country. And with Charlie Weis directing things for the next 10 seasons, this really good team will only get better.
  4. Other good football conferences are the Big 10 and the Big XII. The ACC is okay, and the Big East is overrated - but not nearly so much as the PAC-10.
So, in general, prefer the SEC or the Notre Dame game. Avoid the PAC-10 game. Check out the Big 10 or the Big XII to see if there is a game you shouldn't miss. That should keep you busy for the weekend.

A couple of other pointers. First, a BYU-Notre Dame matchup is usually good fun. BYU likes to make this into a "religious war" of sorts. I don't think Notre Dame really views it that way. The facts are, Notre Dame is usually orders of magnitude better than BYU, so they usually win, which causes many BYU fans a bit of consternation.
Actually, any game where BYU will probably be destroyed is generally a lot of fun.
Outside of that, don't concern yourself much with any conferences west of the Rockies. The PAC-10 is overrated, as I said, but at least they can blame the stupid media for that. The MWC and the WAC, however - well, they overrate their own selves. Nobody else thinks they are that good. There are some obvious exceptions (Utah in 2004 for example), but one good team does not a conference make (USC and the PAC-10 for example).
Don't concern yourself with the Utah State game, if it is even on TV. Sadly, my alma mater is pathetic at football. If you are cheering for USU, you will just become frustrated; if not, you run the risk of witnessing an embarrassing upset if the improbable should happen.

Bottom line, stick to the SEC, Notre Dame, and key Big 10 and Big XII matchups and you will have a very satisfying season of college football.


Predictions? Well, what do I know? Nothing. I'm not a sportscaster. But hey, they seem pretty clueless also - after all, they are the ones who keep saying that the PAC-10 is good!
I won't name teams. I'll just say the following - this is how it SHOULD be:

First - if any SEC team goes undefeated, they deserve a national title shot. They have the toughest conference in all of football (including NFL, excluding possibly the AFC West).
Second - if Notre Dame goes undefeated, they also deserve a national title shot. They play top teams from many different conferences, having to adjust to many different styles of offense and defense. Tough.
Lacking that, my guess is that the national champion will be the conference champion from either the Big 10 or the Big XII.

Of course what we might get is another matchup against USC, since it is much easier to run the table in the PAC-10. Which will be fine in one sense, in that we get to watch them lose again. But it will also mean that another deserving team gets shut out (think Auburn and Utah 2004), which is a problem.

Thursday, August 24, 2006

The Ultimate Office Layout

Recently at work, a mail thread has been going around about the "Ultimate Office Layout" for software developers, which basically consists of some hogwash about how much better it is to stick all the developers together in one large room, with tables instead of desks, so they can interrupt - er, I mean, collaborate with each other whenever they feel like it.

BS, I say. This is a ploy by subtle managers to convince their engineers that this is the great, new way for a better workspace. They do this by using words like "collaboration" and "productivity." In reality, it is a scheme to control the employee populace by making it so they can be observed all the time. Hey, why not make us stand up all day long? And program using Commodore PETs? Why not display the contents of my monitor up on a large screen where everyone can see? Why not make me only use the telephone if it is on speaker?

Ugh. I don't buy into it. Good engineers know how to work well and they don't need some new-age high-productivity layout to do it - and lousy ones will be lousy regardless. Fortunately, my employer has not bought into this garbage. Yet.

But they might need some counterpoints, some ideas with which to refute this nonsense. Thus, I present to you, the ultimate office. Please pardon the crude drawing.



Description of The Ultimate Office:
1. The primary monitor - a 100" screen from a front-projection monitor in the ceiling near the center of the room.
2. The secondary monitor - another 100" screen like the first.
3. Center 7.1 surround channel - two 6 1/2" woofers and one 1" horn tweeter.
4. 7.1 surround satellites (left and right) - one 6 1/2" woofer and one 1" horn tweeter.
5. Media cabinet with PCs and media server, 7.1 surround sound receiver and amplifiers, audio mixer.
6. 7.1 rear satellites (left and right) - one 6 1/2" woofer and one 1" horn tweeter.
7. 7.1 rear speakers (left and right) - two 6 1/2" woffers and one 1" horn tweeter.
8. Recliner/office chair.
9. Primary work space.
10. Whiteboard discussion/meeting space.
11. Love seat (preferably leather).
12. Sofa (again, leather).
13. Microwave.
14. Refrigerator.
15. Kitchenette w/ sink.
16. Round table for meetings.
17. Door - solid wood, with no windows, that closes.
18. Very large whiteboard.
19. Light dimmer switch.
20. Bookcase.

Oh yeah. I can see myself getting a lot of work done in a place like that, for sure.

Thursday, August 17, 2006

My Ears Are Ringing

Okay, not really. I mean, not anymore. But my voice is still gone. I saw Journey and Def Leppard last night in concert, with Amber, Greg, and Stephanie, and it was KILLER.

Journey opened. I'd seen them before, a couple of years ago. Journey is a great live act. Don't go expecting a bunch of touchy-feely heart-melting love songs, though. You'll get a couple of them, but Journey live is a first-class arena rock concert. I have to say that Jeff Scott Soto, filling in for Steve Augeri at lead vocals, did an outstanding job. Journey was awesome, leaving some big shoes for Def Leppard to fill - which they almost did, but not quite.

Still, Def Leppard live is a fantastic experience. There is something really magical and polished about their delivery, with each song feeling like it's own unique showpiece, produced to an exacting method. This does have the effect of causing it almost to feel NOT like a concert. I'd never seen Def Leppard before, and it was really awesome.

Best songs of the night:
Star-Spangled Banner (Neal Schon - Journey)
Lovin', Touchin', Squeezin' (Journey)
Lights (Journey)
Don't Stop Believin' (Journey)
Escape (Journey)
Chain Reaction (Journey)
Separate Ways (Journey)
Let It Go (Def Leppard)
Hysteria (Def Leppard)
Rocket (Def Leppard)
Photograph (Def Leppard)
Armageddon It (Def Leppard)
Rock Of Ages (Def Leppard)

Best song of the night - Rock Of Ages. Hands down. That song was MEANT to be played live.


And to think - I could have been at LinuxWorld, heading a Birds of a Feather session. Hmm. Sorry, but I'll take the concert any day. Thanks, Journey and Def Leppard, for giving me a reason to not go. And to that poor sucker who had to go instead of me - well, thanks too.

Thursday, August 10, 2006

Pastrana Flips Twice - At The Same Time

In case you hadn't heard, Travis Pastrana made history at the 2006 Summer X-Games when he pulled of the first-ever double back flip in freestyle MX competition.

He also made history by riding his motorcycle without injuring himself, although he apparently did blow his knee out later by walking on it.

You can't help but like Travis, but at the same time he has been a pretty big disappointment. The 2000 125cc AMA National Champion and 2001 125cc AMA Supercross Champion could have had a huge impact in Supercross. He could have continued what McGrath started, taking the popularity of Supercross to a new level, because of his great personality and riding skill. Instead, he is so distracted by so many other things, like freestyle MX, that we'll never know what could have been.

Still, if you haven't seen this video, you'd better give it a look. It's pretty awesome.

(Head on over to expn.go.com for more X-Games videos.)

Tuesday, August 01, 2006

Rules for Driving

Well, since I gave you the rules for parking, I thought I probably ought to also supply the rules for driving. Like the rules for parking, if you are a half bad boy, you already know these rules.

By the way, I wish to assert the belief that anyone who drives stupidly and thus causes road rage that escalates into a tragic circumstance shares some of the responsibility. No, I don't know if I really believe that.

1. Don't speed in residential areas. Hey, there are kids at play. Do I really need to explain this one? Nobody thinks you are a stud for speeding through the neighborhood. Mostly, we think you are a jerk.
2. Pay attention to the speed limit - and drive it. Nothing causes me more road rage than someone who isn't driving the speed limit, blocking traffic.
3. The left lane is for passing. Not simple cruising. This is mostly for people in Colorado who suffer from CDD. Hey, Coloradans - get out of the fast lane!
4. Know where you are going before you leave. This might seem obvious but if you have ever driven a car in Utah or Idaho you know that it is not. People will be driving down the road, two lanes each way, in the right lane, and suddenly decide they need to turn left. Right now. Did they forget where they were going? Or did they just decide?
5. Driving is not a contest. If someone passes you, it is not a personal attack. Really.
6. Don't make unprotected left turns across heavy traffic. This is how accidents happen. Turn right and go the "long way." You'll find it is probably actually quicker. (BTW, "unprotected" = "lacking a traffic sign or light that gives you right of way.")
7. Horsepower is a safety feature. It gets you out of trouble in a pinch. So floor that sucker! When the light changes, get a move on! We're waiting back here.
8. Your car is a reflection of your personality. You drive a Citroen 2CV? I don't know what to say about you.
9. If you have an awesome stereo, you can listen to whatever you want as loudly as you like.
10. When you are done driving and get home, park in the garage. The garage is not a big storage shed for all your crap. If you can't fit your car in the garage, get rid of some crap. Yes, I know this sounds like a rule for parking. It kind of crosses over.

Monday, July 31, 2006

Rules for Parking

If you are a half bad boy, you already probably know the rules for parking. But you might be an aspiring half bad boy; a half bad boy in training; a padowan learner. Fear not, aspiring youth. Read on, and you will know how to park like a true half bad boy.

1. The enemy of a good spot is the perfect spot. Are you one of those people who agonizes over trying to determine the absolute closest spot available? Stop it - you are embarrassing the rest of us. Just pick a spot and park. Who cares if it is an extra 50 feet from the door? You could use the exercise.
2. Don't wait for people. Unless the parking lot really is empty, don't wait for people to vacate a spot. Now, I'm not talking about failing to yield to people who are actually backing out when you get there. I'm talking about sitting there, blocking traffic with your turn signal on, waiting for them to get into their car and leave. If you had just taken that spot about 100 feet ahead, you would already be in the building by now. You are wasting everyone's time.
3. Prefer a spot in front of the door - even if it is not the closest. Why is this? Simple - you will always know where your car is without having to remember.
4. Park correctly. This means parking straight, within the spot, not obstructing traffic or other parking efforts, etc. People will judge you by your parking prowess - at least, I will (you lame-parker, you). Oh, and another thing - only one spot per car, please. Only experienced half bad boys know the intricacies of how to get away with quad-parking. Leave that to the experts.
5. Exceptions for really dope rides. You have an H2? Really? Or a blinged-out Escalade on 22s? Or a Ferrari? Man, you are a half bad boy. You can park wherever you want.

Wednesday, July 12, 2006

How to Play Sim Survivor

I figured since I mentioned Sim Survivor last time, I should tell you how to play.

It is really quite easy.
  1. Create a new family with eight people in it. We would do more than eight but families can only have eight people in them.
  2. Start a game with this family in a home that you will build.
  3. When you build the home, focus only on exterior walls. The home should have a fridge inside and a front door. Carpet, wallpaper, furniture, bathroom, beds - all optional.
  4. When the home is built, get everyone to go inside the home. Then pause the game and remove the door.
  5. The game is on! Eventually you will run out of money and there will be no food in the fridge.
  6. The last person still alive is the winner. Enter the cheat code to give them $1M, and then give them some food - fast!
  7. Now that they have won, they can blow their $1M on crap, just like the winners of real Survivor do.
Some considerations:
  • The spartan game (empty rectangular house with a single fridge) is interesting enough, but adding some creature comforts, like a toilet, one or two beds, or a couch can make things more interesting. This way, some of the Sims will be more rested than others, more happy, etc.
  • Building a smaller house increases the likelihood of unhappiness. Not only are people more likely to be standing (and sleeping) in trash and filth, but they are more likely to get in fights. If you are lucky, some of the contestants will give up and quit the game. They will also try in vain to leave.
  • For added zest, include a very junky stove. Odds are pretty good that they will start a fire, and with no front door for the firemen to enter, you have to hope it will just burn itself out. This is a good way to expedite the reduction in contestants, although it sometimes you end up with no winner of the game (for example, the Sims sometimes get so sleepy, that they can't help but fall asleep right in the middle of the fire).
  • You will find that the neighbors come by to meet the new move-ins, and will die of starvation trying to find the door. If you care whether the others in your game survive, you may have to intervene in creative ways.
  • The winner of the game may find his/her home haunted with the ghosts of the losers in the aftermath.
Have fun, and remember - it isn't true life.