Howdy. I hope my subject line isn't too off-putting.
I am a developer myself, at least I used to call myself that back when I was coding in c/c++ and running around in on unix boxes.
Now I mostly develop reports, but most people don't think of this as real development and in a lot of ways you don't have to get quite so nitty-gritty with the 1's and 0's.
Long and short of this question:
I work for a company which uses primarily contract developers, and in dealing with these people I find that the vast majority of my questions are dealt with in the following ways:
1. ask why I am taking the approach I am taking and then suggest other avenues which won't offer the result I am after.
2. prefer to just do the work for me for $ reasons or thinking it will be quicker/easier than explaining some part of their database to me.
3. Consistently and obviously assume I do not know what I want or need or how to do even the most basic of data processing.
I am sure some of this stems from my own presentation of myself, I often do assume that these folks know more about their specific area than I do, THAT IS WHY I AM ASKING THEM QUESTIONS. I do not understand why there is an immediate assumption that I don't even know what a database is when I am asking questions about materialized views, etc. Arg.
Surely some of this post is venting, but I really do want to know if others in semi-dev positions often run into this and if so how do you keep your cool and just deal?
Thanks.
I am a developer myself, at least I used to call myself that back when I was coding in c/c++ and running around in on unix boxes.
Now I mostly develop reports, but most people don't think of this as real development and in a lot of ways you don't have to get quite so nitty-gritty with the 1's and 0's.
Long and short of this question:
I work for a company which uses primarily contract developers, and in dealing with these people I find that the vast majority of my questions are dealt with in the following ways:
1. ask why I am taking the approach I am taking and then suggest other avenues which won't offer the result I am after.
2. prefer to just do the work for me for $ reasons or thinking it will be quicker/easier than explaining some part of their database to me.
3. Consistently and obviously assume I do not know what I want or need or how to do even the most basic of data processing.
I am sure some of this stems from my own presentation of myself, I often do assume that these folks know more about their specific area than I do, THAT IS WHY I AM ASKING THEM QUESTIONS. I do not understand why there is an immediate assumption that I don't even know what a database is when I am asking questions about materialized views, etc. Arg.
Surely some of this post is venting, but I really do want to know if others in semi-dev positions often run into this and if so how do you keep your cool and just deal?
Thanks.