2 ms·
The argument isn't so different from saying that we don't want to distinguish "front-end" and "back-end" programmers. I don't want to distinguish front-end and
by joe_the_user 16y ago
The argument isn't so different from saying that we don't want to distinguish "front-end" and "back-end" programmers.
I don't want to distinguish front-end and back-end programmers. I would like to distinguish front and back-end development.
I do everything currently but I still need put on a conceptual "testing hat", "GUI hat" and "back-end hat". That requires mental effort and costs time. A real Q&A would save that even if I was exactly as skilled as the Q&A person.
- MartinCron 16y agoConceptual distinctions like that are great. I wish more people could be up front about the multi-modal nature of software work.
- ibejoeb 16y agoYeah, that's true. I think the point of the source is that the first line of defense is with the originator of the code. Sure, the context switch is expensive, but that's the price of higher quality. It's not really about firing the QA team. Instead, it's about having a QA function that does not entirely relieve the original author of his duty to ensure quality.