So I’ve noticed something at the last few companies I’ve worked at, including this one. And it seems be correlated with this new movement toward “agile” methodology. “Agile” is just one of the many “get work done” formulas companies adopt to get deliverables out the door faster. It’s a grand tradition–every few years there’s some new approach, usually peddled by think tank snake oil salesmen, promising to “more, faster, and better”. They’re like diet fads, and just as effective. You only ever hear “agile” and “waterfall”. Sometimes “kanban” and “scrum” are thrown around, but it’s all Agile. Or at least it tries to be. See, the thing is, all I…
-
-
Why Developers Should Not QA
The new hotness in software development is Kanban. Kanban’s like an assembly line. As soon as one person’s done working on a thing, they shove it along the conveyor belt to the next, like manufacturing a car. But sometimes things bottle neck at one station or another. So when that happens, you take the people who have free time and put them on something else. They don’t do as good a job as the worker dedicated to that station, but it’s better than nothing. In the software engineering world, that means Business Analysts can do QA and development. QA does development and software analysis. Developers do QA and build business…
