Can one person be two things?

re: Can one person be two things?

Ken Smith — Wed, 27 Jun 2007 02:32:46 GMT

I suppose it's possible to be more than one thing, but the further apart from each other those two things are, the harder it is to be an expert at both. Database guys are generally real experts on only one or two databases, and dabble in the rest. That said, if you can find someone whose brain is plastic enough to wrap their heads around multiple subjects, not get intimidated, and keep learning, you've found somebody worth keeping.

http://smithkl42.blogspot.com/2007/06/universal-dabbler.html

re: Can one person be two things?

Tom Eble — Wed, 27 Jun 2007 17:01:08 GMT

In my experience, it is much easier for an automator to become a domain expert, than for a domain expert to become an automator. First, automators usually have a background in programming. At the least, they have usually taken some programming in college, or have equivalent experience. Second, it is natural for an automator to become a domain expert over time. In order to get automation tasks done, one needs to pick up domain knowledge, and that knowledge will grow over time. Conversely, domain experts typically do not have the time similarly allocated to pick up automation expertise.

re: Can one person be two things?

alanpa — Wed, 27 Jun 2007 19:21:29 GMT

Tom - although I didn't say so above, I definitely agree. There are going to be some people who *can* learn programming, but coming into the profession with some knowledge of logical constructs and computer architecture will make them better testers in the long run.

Thanks for taking the time to comment.

re: Can one person be two things?

aschoolorg — Fri, 29 Jun 2007 20:41:22 GMT

I apologize to being dense.

What are "testers"?

Alan Gregory

re: Can one person be two things?

anutthara — Mon, 23 Jul 2007 18:35:59 GMT

Can two people think the same thing at nearly the same time? :) I was wondering about exactly the same thing recently.

I am on a team that is developing a testing tool. So, when my PM tells me that the target user is a domain expert and not a tester, I can understand if his target customer is only that. What I cannot understand is why we have to assume that the domain expert is braindead when it comes to testing. Are these 2 mutually exclusive things? I dont think so.

And I agree with Tom on the first point - programmers can acquire domain knowledge, but vice versa with no programming background may be a bigger problem. You see folks at MSFT who acquire domain knowledge in the product all the time - the only constant common being they are all great programmers. So, I guess I can completely understand our SDET hiring philosophy