|
 |
Orchid XP v8 wrote:
>
> Is every house *exactly* the same? Probably not.
>
Umm, actually ... a builder can build multiple copies of the same
floorplan, with only minor changes. So, the builder may have 5 different
models in an neighborhood of 1500 houses ...So, it pretty much is the
same for the majority of houses.
Once you've framed a wall, you pretty much know what it will take to
frame the next wall. The framers do not have to sit out there and draw
in the sand to figure out *how* to frame a wall. They just do it. Not
only that, but in many cases the wall components are dropped off at the
site with markings designating where that piece goes, and where all of
the other pieces attach. Not at all like a software program, where
you're figuring out how to do something.
Even better when the builder is using a prefab method, where wall
panels, trusses, and other components are built in a factory, then sent
to the site.
And in the factory? The pieces get cut by big automated saws, dumped
into a bin, and carted to an assembly jig where a laser projects the
outline of the pieces, the pieces have markings on them to designate
where to go, and (at least in the case of complex trusses) a set of
automated pucks have lined themselves up on the outside, so all they do
is pop the chords down, then drop in the webbing according to the
diagram they see on their screen or projected on the table-top.
>
> If you're a company that specialises in writing stock control systems,
> you probably know a thing or two about how to make a stock control
> system work. But, of course, every client is different, so you can't be
> completely sure how hard or easy it will be this time...
>
Yes, but if you're wanting to develop a new stock control, you'll need
to figure out how to draw and create interaction for that particular
control.
>> Every piece of code you write is a *new* piece of code, you are never
>> repeating the same task again.
>
> Sure. I won't argue with that.
>
--
~Mike
Post a reply to this message
|
|
