|
|
Posted by Neredbojias on 10/02/23 12:01
Well bust mah britches and call me cheeky, on Sat, 26 Jan 2008 19:44:33
GMT dorayme scribed:
> Is including the bottom of a cup a design or engineering decision?
A designer could not design a cup without a bottom; it is basic to the
item.
>> Uh, let's try a car. A designer designs a car. It's to be a sports
>> car and should be small and light but powerful. He determines the
>> shape and can guage the size and appx weight. He decides the engine
>> should be about 280 hp or more to overcome the necessary weight, wind
>> resistance, etc., of the impending vehicle. However, there is a
>> limited anount of room under the hood and no currently-produced
>> engine fits the bill. Ergo, an engine must be _engineered_ to meet
>> the requirements _if possible_ or the designer must be informed that
>> a change in engine-compartment size is really necessary.
>>
>> Make sense now?
>
> No.
>
> I understand what goes through the mind of an engineer designing
> something. I just don't understand your categories. You seem not
> to understand the idea of functional design. Perhaps you have a
> coat-of-paint theory about these things: as if there is the
> boring old bits about making something and then there is the
> aethetics, some functionally irrelevant aspect like the actual
> tint or colour it. You identify aesthetics with the most
> superficial but, in fact, least really aesthetic aspects.
>
> And, no, this is not about semantics, it is about a whole aspect
> of design that you seem to leave completely out no matter what
> your words.
Okay, forget it. I give up.
--
Neredbojias
Riches are their own reward.
Navigation:
[Reply to this message]
|