>We sure need to know many things to do our job well (developing solutions for our clients), but with the fast development in technologies, we can't be experts in software and hardware at the same time. There simply not enough time for this.
>
>I've drawn a line between software and hardware knowledge where I learn enough about hardware to do my job, but refer to an expert in hardware when I need to.
>
>I prefer being an expert in one domain than a person who know many things but master of none.

---

>

No doubt, I don't think I'll ever be accused of being an "expert" with hardware, but I can build a computer and troubleshoot them. I can build cable and troubleshoot cable problems without too much investment. These are things I learned while working with a group that had "experts" in each field. As for drawing the line between software and hardware, I don't see that as the line. The line is mostly on the software side. What does being an "expert" really mean? If you can install an NT Server with Back Office, does that make you an expert? I think not, so expert is a subjective term. I try to learn enough about the OS and my systems so that I am comfortable with what I do. When I run into problems that are beyond my experience, I bring someone else in. We all do this right here on the UT. How many times have I used the API gurus code because I didn't know how to do something?< G >