Droid Engineer Archive
Thread: Shields Up! Complete DH profession proposal
Page 4 of 4
Pentaryl
Sat Jan 24, 2004 6:36 am
#41
---------
BlueMorgoth Said:
1) An engineer is good at designing stuff. He is not necessarily good at
using what he has designed. He may know the basics, but doesn't really
have an intimate understanding of all the quirks.
---------------------
I'm a software engineer. I'm really very good at what I do, as I am sure the above poster is good at his job. If I don't know everything about how the software I design is going to be used and how it works, I can't create it or debug it.
I have lots of friends who are engineers in various disciplines. Engineering is all about having an "intimate understanding of all the quirks." Without such an understanding, we couldn't do our jobs.
While it's true that the guy who designs a rifle might not understand how best to use that particular bit of engineering in a military situation, droids are not such simple devices. They are more akin to computers than revovlers.
I would have no trouble with a system that gave bonuses to combat professions for the use of combat droids. Someone experienced in combat should have a better idea how to use a droid in combat than the engineer, but the engineer will have a much more precise knowledge of exactly what that droid can and cannot do and how to get it to perform to it's limits.
Military technology is designed to be used by people under extreme pressure. It's made to be as simple to use as possible in order to keep the possibility for errors in a battlefield situation as low as possible. I would imagine the same would be true of any military droids.
I can easily understand that the use of droids might be restricted by law, as is the use of military technology.
I think a certification or license system makes far more sense than another skill tree that will make it even harder for people in the DE profession to have any flexibility in this game.
BlueMorgoth Said:
1) An engineer is good at designing stuff. He is not necessarily good at
using what he has designed. He may know the basics, but doesn't really
have an intimate understanding of all the quirks.
---------------------
I'm a software engineer. I'm really very good at what I do, as I am sure the above poster is good at his job. If I don't know everything about how the software I design is going to be used and how it works, I can't create it or debug it.
I have lots of friends who are engineers in various disciplines. Engineering is all about having an "intimate understanding of all the quirks." Without such an understanding, we couldn't do our jobs.
While it's true that the guy who designs a rifle might not understand how best to use that particular bit of engineering in a military situation, droids are not such simple devices. They are more akin to computers than revovlers.
I would have no trouble with a system that gave bonuses to combat professions for the use of combat droids. Someone experienced in combat should have a better idea how to use a droid in combat than the engineer, but the engineer will have a much more precise knowledge of exactly what that droid can and cannot do and how to get it to perform to it's limits.
Military technology is designed to be used by people under extreme pressure. It's made to be as simple to use as possible in order to keep the possibility for errors in a battlefield situation as low as possible. I would imagine the same would be true of any military droids.
I can easily understand that the use of droids might be restricted by law, as is the use of military technology.
I think a certification or license system makes far more sense than another skill tree that will make it even harder for people in the DE profession to have any flexibility in this game.
Page 4 of 4