Talkie Walkie Trustie

re: Talkie Walkie Trustie

The Braidy Tester — Wed, 09 Mar 2005 17:49:00 GMT

We find tester-developers in lots of places. See http://blogs.msdn.com/micahel/archive/2005/03/09/390865.aspx for the full skinny!

re: Talkie Walkie Trustie

AdamU — Wed, 09 Mar 2005 06:18:00 GMT

How do you find them? It's not easy, but hiring never is. I talk to potential candidates about the strong technical challenges associated with the SDET position. I also frame the conversation on the differences between SDE and SDET (because it always comes up) in terms of problem spaces, breadth for SDET and depth for SDE.

re: Talkie Walkie Trustie

Mark Eichin — Thu, 03 Mar 2005 20:56:00 GMT

So how *do* you find tester-developers? Certainly a job description that says "QA" seems to be an invitation for lots of resumes from script-followers. I want people who think repetetive tasks are what computers are for, not people, and that "poking at the interface" is exploration to help identify test automation to write.

re: Talkie Walkie Trustie

Jonathan de Halleux — Thu, 03 Mar 2005 04:34:00 GMT

I'm not sure I agree with what the paper says. The author advocates using all kind of languages "that suits best the situations". In theory this is very nice and powerfull, scripting languages are nicer for certain situation, etc... The problem of this model is versioning and maintinability: what will happen in the future ?

Imagine that you arrive in a project that used 5 different scripting languages and harnesses to test it's product. You will have to learn/analyse/run/debug/maintain all the tests in 5 languages. Meaning you have to learn those, even if they are deprecated at that time. This definitely sucks.