|
PIEBALDconsult wrote: Tester's. They have no responsibilities.
Until everyone looks at the tester and asks "why wasn't this bug revealed in testing???"
Marc
|
|
|
|
|
PIEBALDconsult wrote: Tester's. They have no responsibilities. Whoa! You better hire some new testers. We have the best QA guy. He has the patience to test every single little detail and he is awesome. He finds so many bugs that get past dev that by the time we release we have a very solid product.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Yeah - a good tester in a culture that respects them (instead of taking each ticket as a personal insult) is worth his weight in gold.
Regrettably, most devs behave like children when told "you made a mistake here".
Herself was the QA department for a wiring harness company for a while. (12 weeks as it turned out) Their attitude was "we don't make mistakes" and refused to let her have time to even do batch testing. The company is no more, after a bad batch of cables destroyed a lot of customer equipment at just the wrong time.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Regrettably, most devs behave like children when told "you made a mistake here". I've heard that they exist. I've been very fortunate to never have worked with one.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
OriginalGriff wrote: "we don't make mistakes"
Hey! I think I interviewed a developer from their IT department. I believe the direct quote when asked about how he tests his code before moving it to QA was "I don't. There are never mistakes in my code. If the user ever reports a bug then it is because they were not properly trained."
We didn't hire him.
|
|
|
|
|
Herself here used to design the wiring harnesses/looms for heavy trucks.
She says she used to look forward to new designs coming back with queries/complaints, because fixing the "bugs" was more interesting than doing the original designs.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
PIEBALDconsult wrote: Tester's. They have no responsibilities.
I am certain you are joking, but unsure.
|
|
|
|
|
Slacker007 wrote: I am certain you are joking, but unsure. I think some testers only execute test scripts, don't actually do much themselves. Perhaps that is what he is referring to.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Those aren't testers: they are burger flippers in a different job...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Aside from what I do now I have always been a test tech - albeit hardware and embedded firmware. Oh it a gravy train. 8-5 Monday - Friday 2 weeks vac health and dental , profit sharing etc..
Was a different time when America was bitchin and Reagan was in the white house though.
|
|
|
|
|
|
I always wondered what customers were for?!
|
|
|
|
|
|
Nothing is relaxing by nature. In the end, all that matters is the perception.
1. A Developer thinks, it's the tester who is relaxed as he don't have to code.
2. A Tester thinks, it's the developer who is much relaxed as he don't have to test.
I assume you are a developer
Ranjan.D
|
|
|
|
|
During work, or in general?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Good question. I guess after work, a certain amount of garbage collection runs on developers mind and obviously he is not relaxed
Ranjan.D
|
|
|
|
|
You mean sleep
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Yeah, now I see where it's going I doubt the OP meant the same for relaxing
Ranjan.D
|
|
|
|
|
That does not really make any sense: anything done professionally is not about relaxing.
Relaxing is when you get out of any professional duty.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
|
|
|
|
|
I dunno - I find software design strangely relaxing and therapeutic.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I like development and software design a lot, since about thirty years now. I find that quite exciting, and rewarding also when I manage to achieve my goals, especially when it takes me quite some time and efforts.
But relaxing comes after all that. When I shut off my computer and go out and see my friends; or finally watch this lovely serie I downloaded weeks ago; or have a glass of dry Cardhu with a good book.
Therapeutic? I've quit the idea to be able to be saved a long time ago
There are two kinds of people in the world: those who can extrapolate from incomplete data.
|
|
|
|
|
OriginalGriff wrote: I find software design strangely relaxing and therapeutic.
Same here.
|
|
|
|
|
If you're good at something, doing it shouldn't be a strain.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
A developer's life is more relaxing.
You only have to write three lines of code a day, and tell everyone it's hard*.
* Don't tell me you haven't worked with that guy. He gets around more than herpes.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Go for tester. Of mattresses. Very relaxed
|
|
|
|