Quote:
Originally Posted by Matt Krass
Traditionally programmers usually get this kind of treatment. The best plan I've seen for fixing it is to get involved in the mechanical side of things. You'll learn more skill-sets, you will be be able to personally design in and mount your sensors, and best of all, you're not 'just a programmer' anymore, so you may have better luck communicating.
Unfortunately, especially with FIRST giving out so much pre-written code (that only sort of works, not that anyone else understands that) people tend to assume the programmers job is point and click monkey.
Matt
|
Now, I am a very "low level" person and my mentor finds me too valuable of a programmer to be doing electronics or any hardware. I try to use the lowest to the hardware the software allows. I have just glanced over the pre-written codes, I was "appalled" by the thought of even copying the method of doing things they use. Plus, I don't like the way they do things anyway. May be that is my personality flaw, but I see it as a good thing. Might hint on the fact that I am arrogant, but shows I am independent. I have been criticized by other programmers because they think I am just making it harder on myself. I like the challenge actually and I feel guilty if I use prewritten code, feels like cheating to me. (Now it really is not cheating per se, but feels very much like it)