Both are aspects of bringing a product to the market, or a process... or anyting... Arcitecture is design , the design of something, like a building, while engineering is independant of what you are designing, but makes the creation of that product possible.
It isn't about one being creative and the other being grunt labor... Neither is true.
One designs what a product will do, the other designs how it will do it.
In general. Houses tend to have an Arcitect and no specific engineer, because how you put the house together in standardised.... so a better example would be a bridge.
Bridge design teams tend to have Arcitects and Engineers, both work together to produce the creative out put... In this case, a bridge design.
Engineers care about how the bridge will stay up and hold its load, the arcitect cares about how the bridge will look.
Sometimes, people can be both...
For example... Most of the coders who hang out here are both. They think up the game idea, then work out how to do it, and they even go as far as to do it... So, they are Architects, Engineers, Skilled workers, and Unskilled workers all rolled into one.
It isn't about one being creative and the other being grunt labor... Neither is true.
One designs what a product will do, the other designs how it will do it.
In general. Houses tend to have an Arcitect and no specific engineer, because how you put the house together in standardised.... so a better example would be a bridge.
Bridge design teams tend to have Arcitects and Engineers, both work together to produce the creative out put... In this case, a bridge design.
Engineers care about how the bridge will stay up and hold its load, the arcitect cares about how the bridge will look.
Sometimes, people can be both...
For example... Most of the coders who hang out here are both. They think up the game idea, then work out how to do it, and they even go as far as to do it... So, they are Architects, Engineers, Skilled workers, and Unskilled workers all rolled into one.