Slashdot Mirror


If Bad Software Developers Built Houses...

Richo99 writes "The editor at UI Hall of Shame takes us for a walk through a house designed by bad software developers. It appears Ed is getting a bit tired of really bad software designs in popular shareware titles. It is interesting because how much of a crime these apps perpetrate isn't obvious until you apply the same logic to everyday things, like the design of a house. I especially love the access to the garden. "

91 of 578 comments (clear)

  1. And the heating system by gbulmash · · Score: 5, Funny
    And if you want to heat the house, you have to light a fire in a firebox outside and then manually pump a bellows to force heated air into the house. The spec had an automated heating system with natural gas, a pilot light, and fans, all controlled by a thermostat, but management only assigned the developers to your project for three weeks and the only way to get the project "finished" in the allotted time was this kludge. But don't worry, it will be fixed in v2.0, which is currently calendared for 2007 by management... unless something they consider more important comes along.

    - Greg

    1. Re:And the heating system by jb.hl.com · · Score: 3, Funny

      I'm sure the guy will have no problems heating his house with the flames that are shooting from his web server right now.

      --
      By summer it was all gone...now shesmovedon. --
    2. Re:And the heating system by jellomizer · · Score: 4, Insightful

      While moderated funny. I think I see the real point. A lot of the time of software failure is basicly management going to the development team and tells them to cut corners to get it done. So you could be the best interface developer on the planet. But if they tell you that it needs to be done now. when you are halfway threw. You end up breaking rules because it is quiker to program .

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:And the heating system by bigman2003 · · Score: 4, Funny

      Well, obviously if he designed a house...

      The roof would cave in when more than 30 people knocked on the front door.

      --
      No reason to lie.
    4. Re:And the heating system by Rei · · Score: 5, Funny

      I'm wondering when there will be a bugfix for the author's writing style.

      I havent seen so many runon sentances and bad capitalization/punctuation and mispelings since Third Grade, theyre really anoying and distracting from the Article, I want my articles written good.

      --
      Sigur RÃs: I didn't know that Heaven had a rock band.
    5. Re:And the heating system by lucabrasi999 · · Score: 2, Insightful
      I want my articles written good.

      In that case, maybe you shouldn't be reading articles that are posted on the internet. Go back to the print media, where they have editors.

    6. Re:And the heating system by SiO2 · · Score: 4, Funny

      I want my articles written good.

      You really meant to say that you want your articles written well.

      SiO2

    7. Re:And the heating system by pegr · · Score: 2, Funny

      I havent seen so many runon sentances and bad capitalization/punctuation and mispelings since Third Grade,

      Welcome to the IntarWeb!

    8. Re:And the heating system by miketo · · Score: 5, Insightful

      You are right in several respects: non-development management has screwed over more projects than it's ever helped. I've seen it and had my projects fscked many a time. One classic was the VP who wanted the acronym "API" removed from the help files for a developer kit. Reason? "We make solutions, not programming software."

      But I *will* point fingers at developers for bad design, too. In the same company I have worked with developers who code up something that neither does what it should, is usable by anyone but them, or can be gracefully fit into the existing programming model. Too often they were called a "temporary fix" for the current release, to be fixed in a future release. It never was, it just became more encrusted with shims, helper libraries, and other complexification / bogger-downers.

      Same goes for UI designed by developers. *UNLESS* you have spent time with the end users seeing what it is they are trying to do, you are not going to hit the mark by coding UI in your cubicle on the mistaken assumption that you know the best way to do something.

      I have seen this happen so many times. I take a developer to a customer site to help diagnose a problem. After only ten minutes, the light comes on in the developer's head and a new solution is created that works, works well, and does what the customer wants and expects. Yet most development happens in reverse: cook up an idea, code it, then see if anyone likes it.

      There's a lot of bad software project management out there, and there is enough blame to go around.

    9. Re:And the heating system by SupremeTaco · · Score: 5, Funny

      W H O O S H!

      --
      You have a constitutionally protected right to be wrong, and I the right to ignore you.
    10. Re:And the heating system by Omnifarious · · Score: 3, Funny

      Now we know why your username is SiO2. You are utterly transparent to humor, it goes right through you without affecting you at all.

    11. Re:And the heating system by computational+super · · Score: 5, Interesting
      If other industries and professions can accurately estimate and deliver product, why can't software?

      Because engineers in other industries and professions spend orders of magnitude more time estimating than they do actually building. (Once the estimating is done, the building is usually fairly straightforward, relatively speaking). We could probably accurately estimate the time taken to build software... but then they'd ask us to estimate how long the estimate would take... and then how long the estimate of the estimate... Or, we could just take a reasonable guess and just build the damned thing.

      And, by the way, no industry or profession can accurately estimate and deliver product. Road construction, satellite design, new home construction, movie production, etc. etc. are always complaining about running over budget. Software is exponentially more complex than any of those.

      In summary, bite us.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    12. Re:And the heating system by legirons · · Score: 2, Funny

      "The roof would cave in when more than 30 people knocked on the front door."

      Like the WindowsXP Pro house, where you can only invite 10 friends at once (and have to get planning permission again every time you get new furniture...)

    13. Re:And the heating system by Ricdude · · Score: 4, Insightful

      This is why building codes state unambiguously how thick joist must be, and how far you are allowed between them, how thick posts must be to hold up a deck of size WxD, how to anchor posts to foundation, what to use for foundation, how deep cement anchors must be embedded in the ground, etc.

      "Standards", as far as software construction, are non-existent. Well, there are some style guides out there, but most of them conflict with most others. "Style" guides usually focus on inane issues like indentation and variable naming, instead of including insightful issues like, "C library functions that operate on strings without checking lengths should not be used: (list of functions to avoid)." Classifications of error conditions and how to recover or adequately respond to them are also usually lacking (what's a warning? what's an error?)

      When issues like this are developed for software, and people actually follow them, you'll see greater consistency in software.

      --
      How's my programming? Call 1-800-DEV-NULL
    14. Re:And the heating system by Hognoxious · · Score: 2, Insightful
      let the developers work out the design; then have a UI team build an interface to the given design.
      Right. Because UI design is just about pretty colours and stuff. It has nothing to do, say, with the underlying mental model and the actions the user might do to what he perceives as the objects in the system. Still, if those don't match what the developers did, we'll hack a middle layer into place. Sigh.
      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    15. Re:And the heating system by e2d2 · · Score: 2, Insightful

      Also, most of the other professions cited have about 1000 years of history leading up to their current state. Engineering and Architecture didn't just arrive in the 1950s.

      But I will add one thing - when will software developers start building better software? When the customer pays for it that's when. Most customers don't accept the schedule or budget for such an endeavor unless they are NASA or similiar organization that demands such high quality. Building such software takes resources, the customer has to be willing to give those resources (time, money, etc). Until that day comes where the customer is ready to give those resources we will not see much change.

    16. Re:And the heating system by Peaker · · Score: 4, Interesting

      Some C library functions that operate on strings with checking lengths should also not be used:

      strncpy - does not guarantee the terminating NULL and fills the dest string with zeroes if it is short (bad performance)

      strncat - does not guarantee the terminating NULL and the 'n' argument is very confusing and encourages buggy calls.

      Use strlcpy/strlcat instead (oh wait, the GNU libc maintainer refuses to put them in...)

    17. Re:And the heating system by Xyrus · · Score: 4, Insightful

      But let's turn the tables here. Let's give the home builders the usual specs that a software developer is given.

      You estimate it will take you 18 months to build the house. The "owner" comes back and says you have eight.

      You say you need specific pieces of wood and nails to build the house with, however the owner tells you to use new unproven materials that don't even have effective methods of working with.

      You say you need specific types of hammers, saws, cement mixers, etc. The owner says you can only use a rusty hammer with a broken claw, a dull saw, and you'll have to mix the cement by hand in a bucket to pur the foundation.

      Your allowed to look at the location your going to build at, but you are not given the resources or time research the ground stability.

      After you have rushed together a blue print, you're told to start. Halfway through, the owner changes the building materials, tells you that the utilities won't be there for another year, and change the complete layout of the house in the process.

      In the last two weeks of frantic work, the town code person changes all the building codes.

      So what kind of house do you get after this?

      You don't.

      And that's how a lot of software comes out.

      ~X~

      --
      ~X~
    18. Re:And the heating system by llefler · · Score: 2, Funny

      The front door is there, but it has no lock. Because the owners would just tape the key to the door anyway.

      Of course, if we did use a lock, our key would be a minimum of 6" long and must be made out of steel, plastic, and at least one bit of glass. Then we would be confused at why the owners found it annoying to carry.

      --
      It is amazing what you can accomplish if you do not care who gets the credit. -- Harry Truman
  2. Of course... by Tuxedo+Jack · · Score: 4, Funny

    If Microsoft programmers built houses, the walls would be blue with white trim, and the garage would have to have CHKCAR run on every instance of the door opening.

    On top of that, there's also the whole "backdoor left wide open" stigma that comes with the Windows house.

    --

    Striking fear in the authors of godawful fanfiction, I am here, appearing in darkness, Tuxedo Jack!
    1. Re:Of course... by Thijs+van+As · · Score: 2, Funny

      Don't forget the big cross right above each window pane!

    2. Re:Of course... by saleenS281 · · Score: 2, Funny

      vs. a linux house where you'd have to ring the doorbell while turning up the thermostat and unlocking the front door all at the same time just to turn on the light in the bathroom.

    3. Re:Of course... by MighMoS · · Score: 2, Funny

      Yeah, but its not hard to create the equivilent of a shellscript for that...its a doohickie thing that looks like an invention out of Dr. Seuess' books.

    4. Re:Of course... by Rei · · Score: 2, Funny

      Microsoft houses would all be factory-built, and 90% of America would use them. Linux homes would all be at least somewhat custom. Builders like Gentoo require that you draw up your own floor plans and hope that it meets code; companies like RedHat offer a selection of houses that they think that you may want to start with. And distros like GoboLinux are putting up fliers on telephone poles on Main Street in their hometown saying "Please Notice Us!!!! Please!!!! We build houses, we swear!!!"

      Meanwhile, Apple would be quietly getting by on sales of high-end igloos and yurts.

      --
      Sigur RÃs: I didn't know that Heaven had a rock band.
    5. Re:Of course... by peragrin · · Score: 5, Funny

      Get it right

      Apple would be quietly getting by on sales of high-end earthen homes.(think hobbit hole) They would include their own wind and solar power supply as well, but need regular line power to work at 100%.

      I also imagine Gentoo would be more like here's an axe, a saw, a hammer, and here is a sample floor plan. There are some good sized trees over there have fun.

      --
      i thought once I was found, but it was only a dream.
  3. If webmasters built houses... by Anonymous Coward · · Score: 2, Funny

    I wonder where dead links stack up... ;)

  4. wow, that house went down fast... by Se7enLC · · Score: 2, Funny

    wow, one comment and it's already /..ed

    that's like a 2mph wind knocking over the house, right?

  5. Already slow; Full Text of Article: by Anonymous Coward · · Score: 5, Informative

    Lets take a walk through a house built by our illustrious legion of very ordinary Software Developers we've seen over the last few posts..

    You arrive at a friends new house and step up to the front door.. well, you do after finding it around the side of the house..

    You press the door bell but dont hear the reassuring ding dong sound coming from inside the house, you ponder if you missed hearing it and wait a few moments before politely pressing it again, this time you're SURE, there was NO doorbell sound coming from inside. You peer at the doorbell, its a button, how much more complicated can it be? You DOUBLE CLICK it and hear a loud DINGDONG coming from inside..

    Your Friend, Herbert's footsteps approach the door from inside and you straighten your tie ready for the door to open. Herbert unlocks the door and the damn thing swings OUTWARDS knocking you back a step or two. Apologetically the owner explains that's how it was when they bought the house "it fools everyone and it'll be a great source of converation at our Dinner Parties".

    You politely chuckle and hope they get the damn thing fixed.

    Herbert invites you into the house, you step unsurely into the hallway and peer around.

    The ceiling has a sort of mauvy pink color, not dissamilar to your Grandmother's slippers, the walls are mostly red.

    Herbert offers you the grand tour of his new home and gestures towards what you assume is the Lounge room thru a doorway off the hallway. You wander in suprised to find that you're in the toilet.. nervously Herbert chuckles and explains that to get to the Lounge you have to pass through the 2 Way Toilet.

    You emerge on the other side of the toilet into a long narrow room that stretches the length of the house, its about 5 feet wide and 45 feet long. At the far end of this poorly lit room you can see a Television. The only light coming into the room is from a small window at about knee height.

    Herbert explains the Lounge Room is really an extension that wasn't planned very well, he invites you into the kitchen through a revolving door. You step into a large circular room after missing the first few exits of the rapidly revolving entrance. In the middle of the room is a large Island Bench, its working surface is about 5 foot high. there's no other furniture in the room, but there's 9 doors evenly spaced around the room. Herbert explains that through each door is an appliance, there's the Fridge Room, the Oven Room, the Freezer Room, the Dishwasher Room, the Food Room, the Microwave room etc.. Its a pain Herbert says, taking things from one to the next, but you get used to it he says... you feel doubtful.

    Herbet is keen to show you the Master Bedroom, but he's not sure which door its through, he tries three then finds the right one.

    As usual, the damn thing opens outwards.. You dutifully but somewhat hesitantly follow Herbert through the Master Bedroom, you wonder what bizarre idea you're going to be introduced to next.

    Herbet gestures around what appears to be an empty room with a self-satisfied smirk on his face. You peer around trying to work out what bizarre idea the builder has foisted upon the house now. "Where's the BED, Herbert?" Herbert theatrically claps his hands together twice and stamps his foot.. the bed silently descends from an opening that appeared in the ceiling, you jump
    out of the way just in time and the bed neatly touches down in the centre of the room. "Neat hey!" Herbert prompts you.. "Ah yeah, thats great Herbert".. You gingerly sit on the bed, it promptly collapses.. "Ah, yeah that happens a bit, you get used to it."..

    "Come and see the Garden!" Herbert excitedly exclaims. Herbet opens a small trap door hidden under a rug and descends a small ladder.. you follow him down. The Garden has a concrete floor and fake concrete trees. There's a wall around it and it has fake grass glued to it.

    You run screaming from the house.

    So, what did we get.. a house built by a moron. Nothing looks, feels

    1. Re:Already slow; Full Text of Article: by saintp · · Score: 4, Funny

      Aaauugh, the typos! Comma splices! Run-ons! My bleeding eyes!

    2. Re:Already slow; Full Text of Article: by quinto2000 · · Score: 4, Insightful

      He forgot to add the price that they paid for this imaginary house: $2,000 with all of the appliances included. You can't complain about commmodity software development not being up to the standards of house building. You need to go to 5 years of school + an internship and then be licensed to build a house, you're paid hundreds of dollars an hour, and you generally are expected to go over budget and over schedule.

      --
      Ceci n'est pas un post
    3. Re:Already slow; Full Text of Article: by EvilNTUser · · Score: 4, Interesting

      "Herbert unlocks the door and the damn thing swings OUTWARDS knocking you back a step or two."

      Wtf... Where I live, all doors open outwards. It's much more convenient*. Interesting assumption coming from a UI critic, who should know better than to accept what he has been given as the best alternative.



      *-The door swings into the yard, instead of creating an obstruction in the foyer.
      -You can close the door immediately, instead of having to take off your shoes and get out of the way first.
      -If a fire breaks out, and a bunch of panicing morons are pushing you from behind, you can still open it.

      --
      My Sig: SEGV
  6. These guys know what they are talking about by Timesprout · · Score: 2, Funny

    Just look at the beautiful design and layout of their site.

    Error establishing a database connection! This probably means that the connection information in your wp-config.php file is incorrect. Double check it and try again. * Are you sure you have the correct user/password? * Are you sure that you have typed the correct hostname? * Are you sure that the database server is running? WordPress Support Forums

    Beautifully crisp, clean, clear and consise

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
  7. The Opposite House by CmdrObvious · · Score: 5, Interesting

    The first thing I thought of was how this house is the opposite of Dilberts house, which is designed by good software engineers.

    http://www.dilbert.com/comics/dilbert/duh/

  8. Doesn't this apply to anything... by InVinoVeritas · · Score: 2, Interesting

    A bad clothes designer turns out crap. A bad automobile designer turns out crap. A bad actor turns out crap. A bad software developer turns out crap. And?

  9. His blog follows a flawed design... by EnronHaliburton2004 · · Score: 5, Insightful

    Oh the irony.

    Perhaps this gentleman should present us with a GOOD DESIGN isntead of just complaining about BAD DESIGN.

    His blog is poorly designed.

    I had a nice eloquent post all written. I hit the "Say It!" button (There is no 'Preview'), and I get to the next page. The next page complains that I forgot to add my email address, so I click 'back', and I'm presented with a BLANK FORM. Everything I wrote was lost, probably because of some wacky Javascript used in his blog form.

    I feel like I entered a bathroom that's 5 feet wide and 100 feet long with a TV at the end.

    I love his design!

    1. Re:His blog follows a flawed design... by RootsLINUX · · Score: 2, Insightful

      I agree. It's easy to bitch about poor design than it is to make a good design yourself. I feel this guy's pain though. I've had my fair share of having to deal with poorly designed/documented software before. A few weeks ago I had to compile this benchmark suite where there was no makefile, no documentation, the only comments in the code were "/********/" to seperate sections of code, and to top it all off, the file extensions were ".cp". So I was like great, is this C code or C++ code? I wasn't able to tell from browsing two files so I said to myself "well, if it's C++ there has to be a class in there somewhere, right?". So I did a `cat *.cp | grep class` and came up empty handed, so I used the c compiler. It was only after the compilation failed with a strange error that I looked up and discovered that the code was trying to referencing something in the c++ library.

      Anyway, due to experiences like that where someone's lack of intelligible design cost me time that it shouldn't have (for god's sake, write your own makefiles!!!) that I become so.....irate when I have to deal with someone else's poorly designed code. I take those painful experiences in mind when I design my own code now though.

      --
      Hero of Allacrost, a FOSS RPG for *NIX/*BSD/OS X/Win
    2. Re:His blog follows a flawed design... by Jeff+DeMaagd · · Score: 2, Insightful

      Worse yet, his site is showing a page that says "403 Forbidden". Yeah, that's a great user interface.

    3. Re:His blog follows a flawed design... by xs650 · · Score: 2, Insightful

      His punctuataion errors have nothing to do with the software problems he has pointed out. His punctuation errors neither increase nor reduce the seriousness of problems with crap software. Crap software is still crap software.

  10. if slashdot editors built houses by professorhojo · · Score: 4, Funny

    would every room be duplicated 2 or 3 times?

    (LOL.. just kidding! don't troll-rate me please! :))))

  11. If builders built buildings.... by thewiz · · Score: 3, Funny

    the way programmers wrote programs, the first woodpecker to come along would destroy civilization.

    Soory, I can't remember who said that, but it is so apropos.

    --
    If "disco" means "I learn" in Latin, does "discothèque" mean "I learn technology"?
    1. Re:If builders built buildings.... by Timesprout · · Score: 3, Insightful

      the way programmers wrote programs, the first woodpecker to come along would destroy civilization.

      Well thats the problem with a lot of programmers, they write instead of building software. Lashing code into an editor is not substitute for a little though and a solid development process.

      --
      Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
      What truth?
      There is no dupe
    2. Re:If builders built buildings.... by lucabrasi999 · · Score: 2, Interesting

      It's one of "Murphy's Laws". Specifically, it is "Weinberg's Second Law". I found it on this page. You might have to search the page. I cannot find a direct link via html.

    3. Re:If builders built buildings.... by ecklesweb · · Score: 2, Informative

      I think you can attribute that to Gerald Weinberg.

  12. Jef Raskin spoke of such things YEARS ago! by CyricZ · · Score: 3, Informative

    Jef Raskin was well-known for pointing out the many flaws of contemporary software GUIs. For those who do not know, Jef Raskin was the man who designed the GUIs for several different Apple operating systems. By the fact that Microsoft borrowed such concepts from Apple, his innovation has also highly influenced the Microsoft Windows platform.

    But anyways, he always stated that GUIs are there for the user, not the developer. GUIs are supposed to be intuitive, so as to allow the user to be far more productive, rather than hindered. Such ideas are not new. Mr. Raskin spoke of such things decades ago.

    --
    Cyric Zndovzny at your service.
    1. Re:Jef Raskin spoke of such things YEARS ago! by jnik · · Score: 5, Insightful
      GUIs are supposed to be intuitive

      Easy to say. The only truly intuitive interface is the nipple.

      Convention leads to consistency leads to familiarity, which is not not the same thing as intuitiveness. Apple understood this--that's really why the platform works, not because it taps some Jungian archetype of computerness.

      It also leads to stagnation, inertia, inefficiencies writ in stone, and claims of mindless copying.

      There are more intuitive and less intuitive interfaces. There are ways to design so as to stay out of the way of the user, or hinder it. But nothing is flat-out, absolute, nonrelative, intuitive.

  13. Vaporhouse... by alexhs · · Score: 2, Funny

    The architect of the house couldn't be joined,
    The foundations aren't ready yet,
    The site is slashdotted already.

    --
    I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
  14. ISO 9002 by Diakoneo · · Score: 2, Insightful

    But if all the quirks are well documented and distributed to all members of the team, well by gosh this is quality work!!! And better yet, if you can trace all the requirements through to the test cases, we can even slap a CMM Level 5 on it!!!

    --
    "Well..here I am..." - Jubal Early
  15. Availability? by scovetta · · Score: 2, Insightful

    Perhaps part of a good user interface would be availability?

    If the owners of this site built a house, it would only allow one person in at a time. The door would remain locked until they left.

    --
    Wer mit Ungeheuern kämpft, mag zusehn, dass er nicht dabei zum Ungeheuer wird. --Nietzsche
  16. and if the UI Hall of Shame built a house by Canonymous+Howard · · Score: 3, Funny

    it would collapse the first time 50,000 geeks tried to visit it.

  17. Mirror! by caryw · · Score: 4, Informative

    Box responds, just not on port 80... someone has the max apache clients set too low. Anyway, MirrorDot mirror:

    http://mirrordot.org/stories/bd14487390c17a50503ea 63520d2685a/index.html
    --
    NoVA Underground: Loudoun, Arlington, Alexandria, Prince William and Fairfax County forums

  18. You beat me to it. by MisanthropicProgram · · Score: 4, Funny
    I was about to say something similar.

    I once asked a management type why was the dealine chosen even the specs weren't even done yet! Their reponse was "that's how we'd meet the ROI (Return on Investment) requirement for the project. I said "Maybe the project isn't worth doing and the VP is an idiot!" , but it came out of my mouth as "Oh I see! I learn something new everyday!" Of course, we missed the deadline and the ROI target too.

    1. Re:You beat me to it. by jnik · · Score: 2, Funny
      "Oh I see! I learn something new everyday!"

      "Specifically, today I learned that the VP is an idiot." (or was that really something new?)

  19. The problem in a nutshell is by beforewisdom · · Score: 4, Insightful

    The problem in a nutshell, going with the analogy is that programmers are not architects.

    They are brick layers and the guys who put in the pipes.

    Imagine a house, built without a design as brick layers and guys who lay piples making it up as they go along.

    1. Re:The problem in a nutshell is by DavidYaw · · Score: 2, Insightful

      The problem in a nutshell, going with the analogy is that programmers are not architects.

      They are brick layers and the guys who put in the pipes.

      Imagine a house, built without a design as brick layers and guys who lay piples making it up as they go along.


      A friend of mine just built a new house, and he compared his old & new... His old house was nothing special, it looked just like the house right next to it, but the architecture made sense: Perfect example: everything that used water (toilets, kitchen, laundry) were located horizontally near each other, so that the plumbing would be nice and simple. In the new house, nothing was near each other, there's probably 100 feet of plumbing (in each direction) in there. I asked "what if this room were flipped the other way around?", and he shrugged, he didn't care either way. With the floorplan he had, simply switching it around so that the toilet is on the left side of the room instead of on the right, would have saved something like 20 feet of plumbing, and wouldn't have changed the rest of the floorplan.

      Additionally, there were other things that weren't "quite right" with the construction: One wall didn't have enough support and it wobbles, a column doesn't line up exactly with the thing it is supporting, stuff like that. So what did the people who lay bricks and pipes do? Probably the same thing we do when a project manager gives us requirements that don't make a lot of sense: Grumble about the idiot that design this thing, it'd be a lot better if you simplified it this way, and then do it anyway, because the decision's been made, the higher-ups have spoken!

      If houses were designed by the same people who design the requirements for software, you'd end up with.... exactly the same thing: Something that looks nice, but would be better designed & better built if they let people who know how to build these things have some say in the design.

    2. Re:The problem in a nutshell is by hey! · · Score: 2, Insightful

      The problem in a nutshell, going with the analogy is that programmers are not architects.

      They are brick layers and the guys who put in the pipes.


      This site has been around for years, and I have to say I've never found it very useful or insightful.

      If you want to know why, just consider the name. When has listening to somebody who sets themselves up to deal in shame and mockery ever been worthwhile?

      It's not that there isn't a problem with user interfaces. There is. And its not that many of the examples they have aren't egregious. They are (although they're off the mark in their analyses in several cases).

      I've done a lot of user intefaces over the years; some bad, some, I think pretty good, none of them perfect. I've learned a few things about them. The first is that almost any product is going to have flaws, some of them serious, most of which can be lived with. But serious or superficial, they're always easy to spot. What is hard is overcoming organizational inertia to get them fixed. Usually, there is no money to be made fixing it, which is pretty much the final word. You can get money to snazz things up with fancy graphics, but you can't get money to make them actually work better.

      So, these hall of shame guys don't get any kudos from me, because what they're doing in my view is too easy. They aren't creating new methologies that quantifiably user performance. They aren't creating organizational strategies that improve products. They aren't creating a user constituency for better interface among users or manmagers. They arent even using these examples as case studies for how a user interface can be improved.

      They're settting themselves up as pontificators and dealers of shame and mockery to people who don't measure up to their standards, without lifting a finger to help them. If I wanted that, I'd join a church.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  20. as usual by tomstdenis · · Score: 2, Interesting

    bad comparison. Just because you have a copy of VB.NET does not make you a software developer. A developer does more than just code which is what a lot of these "self-taught MS-fanboy geniuses" fail to hit.

    This would be like comparing the typical HomeDepot customer to the architect that designed a nearby well standing skyscraper.

    Yes it's fair to say there is a lot of shit software out there. No, it's not fair to say that's the example of a proper software development cycle.

    So in otherwords, this is yet another sensational bit meant to get people like me who should be working, typing up lengthy replies on slashdot...

    Tom

    --
    Someday, I'll have a real sig.
  21. Makes me wonder by Locke2005 · · Score: 3, Funny

    What is the architectural equivalent of doing everything in flash? Las Vegas?

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
  22. Yeah, but... by DavidNWelton · · Score: 4, Insightful

    ... people have been doing houses for several thousand years. We've got the basic idea down pretty well. We've been doing graphical computer systems for how long? 30 years, maybe? And computers, how long have we had those?

    Not to excuse poor design, but sometime's it's easier to piss on stuff than figure out how to fix it.

    1. Re:Yeah, but... by CosmeticLobotamy · · Score: 3, Insightful

      It's not so bad that the article guy pissed on stuff, the problem is he pissed on stuff without being even remotely funny.

    2. Re:Yeah, but... by wheany · · Score: 4, Insightful

      The teacher of our software testing course said that because software engineering is such a young business, people expect the impossible.

      If you were building a house, no-one would come and say that you need to add one more floor that is twice as wide between floors 2 and 3 when you are already making the roof. Oh and it's done in two weeks, right?

    3. Re:Yeah, but... by kfg · · Score: 2, Interesting

      ... people have been doing houses for several thousand years. We've got the basic idea down pretty well.

      No, we don't. Most houses, as they are, are completely braindead. Get thee hence and read "Your Engineered House" by Rex Roberts for some of the ways and reasons.

      And computers, how long have we had those?

      How long have we had mathematics and physical ways of representing it?

      Most software sucks because the people who write it ignore principles that are prefectly well understood and in some cases even provable.

      Garbage in, garbage out.

      Games might be an exception, but then Ed doesn't deal with games, having come to the conclusion that having a bad UI experience must be part of the game, for some reason or other. Beats me why.

      KFG

    4. Re:Yeah, but... by jc42 · · Score: 4, Insightful

      it actually took friggin long for them to come up with the idea for a chimney.

      Here in Boston, one of the fun bits of history is that in 1631, what may have been the first fire ordinance was passed. Among other things, it outlawed wooden chimneys.

      Think about it. There was a reason that they decided to ban wooden chimneys. It wasn't done out of silliness.

      Sometimes I think of this when I see an especially goofy mis-design in some software. I'm also reminded of it by a lot of the anti-regulation rhetoric in this and other forums.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    5. Re:Yeah, but... by pete6677 · · Score: 3, Insightful

      Most houses are not some completely new design that has never been tried before. Sure, there may be different combinations of features, but chances are it's not something incredibly unique. If it is unique, the house will likely be slow and expensive to build with many problems discovered later.

      Software on the other hand, is much more likely to be unique. Nobody requests a word processor to be made for them, they just go out and buy (or "borrow") a copy of Word. Most software development is largely unique, so there are naturally going to be more problems, delays and cost overruns. This is just one reason why software projects tend to be much harder to manage than other projects such as buildings.

    6. Re:Yeah, but... by Anonymous Coward · · Score: 2, Insightful
      If you don't build a wall properly, it will fall down. It's constrained by reality, as I like to say.
      I'm guessing that you have never worked in home construction. Reality is not very constraining. There is a margin for error in home building, and if the margin is exceeded then problems develop later on. Usually these are somewhat minor. People usually don't have walls of there home simply fall down, instead they have nails start to pop out, they notice things aren't square, cracks develop, tiles fall off or buckle, etc. In other words, homes tend to be buggy, just like computer programs. Once you get it to the customer it is their problem to deal with. See, software has learned something from home building.
    7. Re:Yeah, but... by poptones · · Score: 2, Interesting

      It sounds laughable on casual inspection but a chimney doesn't really get that hot past the first few feet. A chimney isn't made to vent fire, after all, but only smoke. And chimneys were not just made of wood but wood and mud.

      Yeah, it seems stupid to make a chimney out of wood - but if it is maintained it's not as stupid a notion as it sounds. Wood is easy to locate, move and stack and it was abundant in the area.

    8. Re:Yeah, but... by Bush+Pig · · Score: 2, Interesting

      Apropos new house designs ... in the 1950's a Sydney architect called Harry Seidler started building houses with flat rooves, and, because people thought they looked really nifty, other architects and builders started making them too. Most of them leaked, because the design hadn't been debugged before they implemented it.

      Oh, and they're really ugly, too (imo).

      --
      What a long, strange trip it's been.
    9. Re:Yeah, but... by HD+Webdev · · Score: 2, Funny

      If you were building a house, no-one would come and say that you need to add one more floor that is twice as wide between floors 2 and 3 when you are already making the roof. Oh and it's done in two weeks, right?

      House structure: Concrete (cough), easy to visualize and understand even by someone without building experience.

      Software: Abstract and evidentally pixies and gnomes are involved somehow.

      --
      This is not a dream, not a dream...we are transmitting from the year 1-9-9-9.
  23. Hilariously bad interior design by Pengunea · · Score: 2, Interesting

    One doesn't have to look far to see bad design manifesting in real life with hilarious effect. The phrase "I'm sure glad I'm already colourblind!" in regards to bad interior design echoes with the sentiment behind "I'm sure glad I never have to work on that project!" in regards to bad software development. In both cases you want to aim the offending subject away from ones' face. However in the case of bad software development not everyone actually walks into the software's spiritual equivalent of the room with the faux fur mauve throw rug in the green-walled room with the gold curtains and the single rusted sink and has a proper around (only to run out screaming).

    I recommend buying the book if you like the sampling from lileks.com. I've seen the collection in it's eye-searing completeness and it's a riot.

    --
    Starkle, starkle, little twink.
  24. As a compensation prize... by Hosiah · · Score: 3, Interesting
    for hardy /.ers now trying to view a dead(?) site:

    http://www.rha.com/ui_hall_of_shame.htm

    http://www.pixelcentric.net/x-shame/

    http://www.raizlabs.com/interface/hall-of-shame/de fault.asp

    These sites all appear to have similar concepts. Don't worry, folks, I'm sure the Meatloafers will be busy guffawing in mulish fashion as they forward the house/UI anology to your inbox for the next ten years after it's no longer funnny.

  25. Re:Software is much more complicated by Ralph+Yarro · · Score: 4, Funny

    a software designer or team is likely to have at least one, if not many, problems that have never been solved before.

    Don't call them "problems", the correct name is "users".

    --

    The real Ralph Yarro posts as Anonymous Coward. Anyone else is an impostor.
  26. As someone who builds houses and software by BoomerSooner · · Score: 5, Insightful

    I have a bit of knowledge in this area.

    Building houses: Very detailed specifications with standards that have been honed over 30-40 years (family business).
    Software dev: Requirements that are never actually pinned down.

    Building houses: Sub-contractors that get paid based on the job, if they fuck up they fix it for free (or lose a valuable account).
    Software dev: If it's broke/bug ridden fees are still paid to develop fixes (unless support built into contract which means you're paying more up front in case there are mistakes).

    Building houses: Customers understand that if they change their mind when the home is in development the cost gets exponentially bigger as the house nears completion. We get bids for change orders and they sign ammendments to their contract approving changes and paying in advance for said changes.
    Software dev: Frequently missed requirements necessitate changes in whole sections of code or UI design.

    If software development weren't so fluid/dynamic it would probably be much like building houses. However a house hasn't changed that much since the 1950's for the most part where computers & software development were happy to be using punch cards. Plus I wouldn't wish city inspectors on anyone in the software industry. Those who can do, those who can't work for the city and are pissed off about it. I love watching city implemented projects with these so called "experienced engineers" who fuck up and have cost overruns on every project they do. It's a good thing city engineers don't have to make a profit or they'd be out on their asses.

  27. These analogies don't hold up by ScentCone · · Score: 3, Informative

    I've never liked these silly "if race car drivers designed shower curtains" type comparisons and conjectures. They don't take reality into account. There's no analogy to hitting "control-shift" in the way you walk down a hall, and 3-D tactile interfaces (like doors, lightswitches) don't have a meaningful representation on the desktop or cell phone.

    Navigating back a couple of pages with your browser (alt-left-arrow) just is not the same as walking backwards out your front door so that you can come into the garage from the side. It's a couple of finger twitches!

    I've come across plenty of crappy interfaces (um, some of which I built myself), and plenty of crappy house designs, too. It comes down to cost. Genius-hatched code, countless hours of user focus groups, and endless release cycles don't jive with reality most of the time. Just like we can't all have dream houses built on the same size lot. A lot of what I've loathed about some software, though, has evolved away nicely over the years through upgrades. Retooling a house to the same degree isn't even something most people can contemplate, and that's reflected in the design and/or the price.

    And: houses have been built for thousands of years. Desktop software for 20-ish. That may seem like an eternity to some Nerd Younglings (meh!) but it's an immature practice/culture in the middle of constant upheaval. The two don't lend themselves to anything other than flame-oriented comparisons, and I'm not talking about sprinkler systems.

    --
    Don't disappoint your bird dog. Go to the range.
    1. Re:These analogies don't hold up by NickFortune · · Score: 2, Interesting
      Look at music history, art history, and any other information-based design work. They've still taken thousands of years to develop. And in thousands of years, I would be suprised if they weren't even more developed.

      I agree with your main point (and that of the GP). On the other hand, software knowledge is evolving faster - at least IMHO.

      The reason for this isn't to do with physical vs knowledge work, it's to do with information flow and feedback times and the population growth curve. People learn what other people have done, and wether it worked or not, faster today than ever before (well, unless last week was a low worm week, but you get the idea). And when they get this info, they react to it, and then add it back into the feedback loop. On top of this, there are more people thinking about these problems than ever before.

      So developemnt times are shortened, and the field matures faster. Of course, the same feedback loop speeds alnost every area of human endeavour - it's just that some like house building are understood in far more detail that others. In these cases, the law of diminishing returns means the speedup isn't so obvious, but I believe its still there.

      As an example, think of electronics, by which I mean wires-and-solder, pre-microchip, non-software electrics. As an industry that's what? A hundred years or so, if we count from Edison who made it a commodity rather than Faraday who doped out the theory anyway. I'd say we understand electrics in a similar sort of depth to house building, but we got there in a far shorter time.

      Of course if you consider, say, quantum mechanics then there's still a lot to be learned about electrons. Of course, the same can apply to construction work, say if you consider space elevators.

      --
      Don't let THEM immanentize the Eschaton!
  28. Part of the problem is ... by crovira · · Score: 2, Insightful

    that we rarely design anything.

    What's cobbled together rarely does the job except it can usualy be faked into something that looks adequate, right until a changed requirement when the whole thing gets tossed into the trash (it was collapsing into it anyway.)

    I find most (hell, almost all,) 'soit-disant' design is missing the basics of software construction principles.

    That we seem unable to do any better, regardless of how often we get burnt, is just WRONG!

    What ever happened to post-implementation reviews? No wonder we seem to be unable to learn anything.

    --
    MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
  29. Apples and oranges by Pedrito · · Score: 3, Insightful

    First of all, I'll be the first to say, UI design in a lot of software, free, shareware, or otherwise, is atrocious. But, comparing it to building a house... That's just stupid.

    Who builds shareware houses? You want to compare, at least compare commercial software, and in that case, commercial software that's not cheap. Otherwise, think about shanty towns for your homes and then start doing the comparison.

    You get stuff cheap, you should expect to get what you pay for.

    On top of which, Software Engineering is a misnomer. It's not engineering. It's not even a science. It's more an art at this point with some aspects of engineering and science.

    Once we have automated tools that can verify a program as bug free (doubt that'll happen in my lifetime), then maybe it can become an engineering discipline.

    With the assumption that your materials are within tolerances (and this can be determined for many), most engineering disciplines have very verifiable results. You can verify with mathematics that a bridge or building won't collapse, assuming your materials are verifiable. You can't do the equivalent with software.

    The same goes for most other engineering disciplines. So the comparisons are invalid for a few reasons. But hey, I'm behind him on what he wants: Better UI design all around.

    My manager was telling me yesterday about an resume he received from a UI designer. The resume was in 7pt type and my manager could barely read it.

    1. Re:Apples and oranges by aduzik · · Score: 5, Funny
      Who builds shareware houses?

      Hey, I build shareware houses.

      • The front door won't unlock for sixty seconds while you stand outside in the rain staring at a nag screen telling you about the terrible plight of the builder (me).
      • The garage has two stalls, but only access to one is allowed.
      • The second floor is "disabled"
      • The bathroom has "limited functionality" (whatever that means)
      • Every thirty minutes, the house kicks you out and makes you reenter.
      --
      If it's not one thing it's your mother.
  30. YOU ALL FAIL IT!!! by Valdrax · · Score: 4, Funny
    I want mine written well, but that's just me. :)

    Yeah, that's cute and all, but maybe you failed to notice the following:
    1. The word "havent" is missing an apostrophe.
    2. The word "runon" is missing a hyphen.
    3. The list of three things that bother him is linked together like "X and Y and Z" instead of "X, Y, and Z."
    4. The word "mispelings" is mispelled.
    5. "Third Grade" is capitalized for no good reason.
    6. The whole latter paragraph is a single run-on sentence. "Third Grade" should end the first sentence, and "theyre" should begin the second.
    7. The word "theyre" is missing an apostrophe.
    8. The word "anoying" is mispelled.
    9. The word "Article" is capitalized for no good reason.
    10. "Article" should end the second sentence, and "I" should start the third.

    Oh, but you'll correct "good" instead of "well" because YOU FAILED TO DETECT IRONY.
    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
    1. Re:YOU ALL FAIL IT!!! by Opie812 · · Score: 2, Funny

      Sarcasm, not irony. ...now that's ironic!!!

      --
      I'm not a nerd. Nerds are smart.
    2. Re:YOU ALL FAIL IT!!! by lgw · · Score: 2, Funny

      For which I want to thank my parents, Ayn Rand and God.
      The Amercian hunter, unlike the Oxford comma, eats, shoots and leaves.

      Use the damn comma. Clarity is the essence of good style.

      --
      Socialism: a lie told by totalitarians and believed by fools.
  31. That's right, pin it on the developers. by Lendrick · · Score: 5, Insightful

    When someone builds a house, they're given a blueprint, which lists the exact specifications for building said house.

    If houses were built like programs are written, it would be a bit more like this...

    Client: Build me a house.

    Developer: What kind of house do you want?

    Client: Oh, the usual. Bedroom, bathroom, kitchen, living room, that sort of thing.

    Developer: Can you be a bit more specific than that?

    Client: More specific? I gave you all the information you need.

    Developer: *shrug* Okay, we'll see what we can do.

    Some months later, a small, nondescript, sturdy house is built. It has a kitchen, a bedroom, a bathroom, and a living room. It lacks certain conveniences like air conditioning and a laundry chute, but the client didn't ask for them and didn't pay for them.

    Client: Looks okay so far, but where's the laundry chute?

    Developer: You didn't ask for one, and we assumed you wanted to keep things simple so you could save money.

    Client: You should have anticipated our needs and put one in anyway. Either way, we need you to add one. Oh, and we'd like you to put on a second story. Some more bedrooms, another bathroom, the usual.

    Developer: A second floor? The foundation wasn't built to handle that. We may have to change the layout a bit so we can add some addition support to the house. Oh, and there's nowhere to put the laundry chute, so we'll have to maybe bring it down through a closet or something. It'll waste some space, but that's the only way we can do it.

    Client: That's fine.

    A couple months pass. A second floor is added onto the house, and support beams are put up all over the place, making the place kind of difficult to navigate. A laundry chute is run down through the front closet, using up about half the space inside it and rendering it basically useless.

    Client: Well... it's okay so far, but now that we think about it, we'd like to *live* in the basement and do our laundry upstairs. Can you possibly make it so the laundry chute will suck the clothes up through it into the upstairs laundry room? Oh, we'd also like you to put another bedroom on the second floor!

    Developer: But there's nothing underneath where the bedroom would go! We'd have to--

    Client: Do it! Why wasn't this done months ago? Also, this whole place looks horrible, and I can't even walk around downstairs without running into a support beam. And what kind of idiot assumes [yada yada yada etc]

    So, whiny clients, if you can't give us *exact specifications*, then you have to learn to deal with messy software, or be understanding when things have to be restarted from scratch. We can build you the house you want, but that's no help unless we know what it is you want.

    1. Re:That's right, pin it on the developers. by drunken+dash · · Score: 2, Insightful

      So, whiny clients, if you can't give us *exact specifications*, then you have to learn to deal with messy software, or be understanding when things have to be restarted from scratch. We can build you the house you want, but that's no help unless we know what it is you want.

      More specifically, they should know what they want.

      --
      Enjoy an e-piphany
    2. Re:That's right, pin it on the developers. by lux55 · · Score: 2, Insightful

      What about cases like shareware or self-made products then, where you're the one who determines what the specification is? It seems to me that most shareware is just as bad as most contracted software, so while I agree with you about contracted software, we also need to be aware that when we're our own customer of sorts (or when we'll be selling something as a product to -- hopefully -- many customers down the road) we need to know how to create specs ourselves too.

      Reason we don't do this is because it's no the fun part. It takes the cowboy out of coding.

    3. Re:That's right, pin it on the developers. by Omnifarious · · Score: 2, Informative

      Your vision of the development process is flawed because you expect the impossible of the client.

      The client can't give you the exact specification, and they never will be able to. You have to design and build in very small steps and get them to look at what you have after every step. That way, you'll never spend a whole bunch of wasted time and effort going down the right path. Also, the client will have a lot more visibility into the project and will be consequently be happier with it because they won't think you made a bunch of arbitrary design choices for your own benefit that they disagree with.

  32. Why the doors swing outwards. by cfalcon · · Score: 3, Funny

    Of course, let's be fair and scale the world correctly...

    Though the visitor thinks that the lounge should be broad and nice, his hostforgets to tell him that he routinely runs horses through at high speeds, and the designer had only the one out to deal with the viscious user having somewhat odd requirements that they insist upon and think are normal.

    The doors swing outwards because there are literally THOUSANDS of travelling salesmen per day, and if it swung inwards they would either force their way in to try to help you refinance your home, sell you vaccuum cleaner enhancements, or have an indecent proposal for your horses... and that's assuming they don't secretly drop self replicating robots inside that use your phones to call up a bunch of misguided teenagers across the world to give them orders like "tear up carpet" and "read house owner's diary to me".

    The garden is plastic because the owner doesn't understand the basics of garden maintenance and anything else would die, and is underground because the sun gives off nova intensity light at random intervals for unforseen amounts of time.

    ---

  33. If Architects Had To Work Like Programmers by JDHawg · · Score: 5, Funny
    This is from an old Air Force Software Acquisition Guide. Enjoy.

    Dear Mr. Architect:

    Please design and build me a house. I am not quite sure what I need, so let's get started. My house should have between two and 45 bedrooms. Just make sure the plans are such that the bedrooms can be easily added or deleted. When you bring the blueprints to me, I'll make the final decision about what I want. Also, bring me the cost breakdowns for each configuration so I can arbitrarily pick one at a later time.

    Keep in mind that the house I ultimately choose must cost less than the one I am currently living in. Make sure, however, that you correct all the deficiencies that exist in my current house (the floor of my kitchen vibrates when I walk across it, and the walls don't have nearly enough insulation in them).

    As you design, also keep in mind that I want to keep yearly maintenance costs as low as possible. This should mean the incorporation of extra-cost features like insulated windows or composite siding. (If you choose not to use Anderson insulated windows, be prepared to explain you decision.)

    Please take care that modern design practices and the latest materials are used in construction of the house, as I want it to be a showplace for the most up-to-date ideas and methods. Be alerted, however, that the kitchen should accommodate (among other things) my 1952 Gibson refrigerator. To assure that you are building the correct house for our entire family, you will need to contact each of my children and our in-laws. My mother-in-law will have very strong feelings about how the house should be designed, since she visits us at least once a year. Make sure you weigh all these options carefully and make recommendations. However, I retain the right to overrule any recommendation you make.

    Please don't bother me with small details right now. Your job is to develop the overall plans for the house and get the big picture. At this time, for example, it is not appropriate to be choosing the color of the carpeting; however, keep in mind that my wife likes blue.

    Also, do not worry at this time about acquiring the resources to build the house itself. Your first priority is to develop detailed plans and specifications. Once I approve these plans, however, I would expect the house to be under roof within 48 hours.

    While you are designing this house specifically for me, keep in mind that sooner or later I will have to sell it to someone else. It should -- therefore appeal to a wide variety of potential buyers. Please make sure, before you finalize the plans, that there is a consensus of the potential home buyers in my area that they like the features of this house.

    I advise you to run up and look at the house my neighbor built last year, as we like it a great deal. It has many things that we feel we need in our new home, particularly the 75-foot swimming pool. With careful engineering, I believe you can design this into our new house without impacting the construction cost.

    Please prepare a complete set of blueprints. It is not necessary at this time to do the real design, since they will be used only for construction bids. Be advised, however, that you will be held accountable for any increase of construction cost as a result of later design changes.

    You must be thrilled to be working on such an interesting project! To be able to use the latest techniques and materials and to be given such freedom in your designs is something that can't happen very often. Contact me as soon as possible with your ideas and completed plans.

    Sincerely,

    The Client

    PS: My wife just told me she disagrees with many of the instructions I have given you in this letter. As the architect, it is your responsibility to resolve these differences. I have tried in the past and have failed to accomplish this. If you can't handle this responsibility, I will have to find another architect.

    PPS: Perhaps what I need is not a house at all, but a travel trailer. Please advise me as soon as possible if this is the case.

    1. Re:If Architects Had To Work Like Programmers by JFKLiberal · · Score: 2, Informative

      Good one! But where is the part where the owner fires the architect and hires another in the middle of construction of his house and wants to keep the completion date the same?

  34. It's also more secure by apankrat · · Score: 3, Funny

    It is really hard to open outwards-swining door with a mighty foot kick :)

    --
    3.243F6A8885A308D313
  35. Re:Doors swinging outward? by EvilNTUser · · Score: 3, Interesting

    "This makes locks on doors absolutely pointless because you can just remove the pins on the hinges and the door will just fall down."

    Doors can be designed to avoid that. I'm not sure what the standard way is, but my apartment's front door, for example, has metal rods embedded next to the hinges. They are virtually unnoticeable to the user, and automatically slide into the wall when the door is closed. This is probably more secure anyway.

    --
    My Sig: SEGV
  36. Re:Terrible Analogy by hurfy · · Score: 2, Interesting

    We just DID.

    and it's NOT!

    Hell, pull up a list of invoices on the screen and it ONLY scrolls forward. At least the doors on my house work in both directions i may want to go...

  37. Re:Doors swinging outward? by zerbot · · Score: 2, Informative

    There are hinges that allow outward opening of doors without exposing the pins on the outside.

  38. If Architects Had To Work Like Programmers by WallyHartshorn · · Score: 2, Interesting
    Sorry, I don't recall where the following came from. Please save it and show it to the next person who compares software unfavorably to houses.
    If Architects Had To Work Like Programmers

    Dear Mr. Architect:

    Please design and build me a house. I am not quite sure of what I need, so you should use your discretion. My house should have somewhere between two and forty-five bedrooms. Just make sure the plans are such that the bedrooms can be easily added or deleted. When you bring the blueprints to me, I will make the final decision of what I want. Also, bring me the cost breakdown for each configuration so that I can arbitrarily pick one.

    Keep in mind that the house I ultimately choose must cost less than the one I am currently living in. Make sure, however, that you correct all the deficiencies that exist in my current house (the floor of my kitchen vibrates when I walk across it, and the walls don't have nearly enough insulation in them).

    As you design, also keep in mind that I want to keep yearly maintenance costs as low as possible. This should mean the incorporation of extra-cost features like aluminum, vinyl, or composite siding. (If you choose not to specify aluminum, be prepared to explain your decision in detail.)

    Please take care that modern design practices and the latest materials are used in construction of the house, as I want it to be a showplace for the most up-to-date ideas and methods. Be alerted, however, that the kitchen should be designed to accommodate, among other things, my 1952 Gibson refrigerator.

    To insure that you are building the correct house for our entire family, make certain that you contact each of our children, and also our in-laws. My mother-in-law will have very strong feelings about how the house should be designed, since she visits us at least once a year. Make sure that you weigh all of these options carefully and come to the right decision. I, however, retain the right to overrule any choices that you make.

    Please don't bother me with small details right now. Your job is to develop the overall plans for the house: get the big picture. At this time, for example, it is not appropriate to be choosing the color of the carpet.

    However, keep in mind that my wife likes blue.

    Also, do not worry at this time about acquiring the resources to build the house itself. Your first priority is to develop detailed plans and specifications. Once I approve these plans, however, I would expect the house to be under roof within 48 hours.

    While you are designing this house specifically for me, keep in mind that sooner or later I will have to sell it to someone else. It therefore should have appeal to a wide variety of potential buyers. Please make sure before you finalize the plans that there is a consensus of the population in my area that they like the features this house has. I advise you to run up and look at my neighbor's house he constructed last year. We like it a great deal. It has many features that we would also like in our new home, particularly the 75-foot swimming pool. With careful engineering, I believe that you can design this into our new house without impacting the final cost.

    Please prepare a complete set of blueprints. It is not necessary at this time to do the real design, since they will be used only for construction bids. Be advised, however, that you will be held accountable for any increase of construction costs as a result of later design changes.

    You must be thrilled to be working on as interesting a project as this! To be able to use the latest techniques and materials and to be given such freedom in your designs is something that can't happen very often. Contact me as soon as possible with your complete ideas and plans.

    PS: My wife has just told me that she disagrees with many of the instructions I've given you in this letter. As architect, it is your responsibility to resolve these differences. I have tried in the past and have been unable to accomplish this. If you can't handle this responsibility, I will have to find another architect.

    PPS: Perhaps what I need is not a house at all, but a travel trailer. Please advise me as soon as possible if this is the case.