Comment by lukan
2 months ago
That is all part of doing the thing called quality software develeopment.
Quick and dirty does not work in all environments.
2 months ago
That is all part of doing the thing called quality software develeopment.
Quick and dirty does not work in all environments.
> That is all part of doing the thing called quality software develeopment
It's all part of doing software development on a team that has embraced the trappings of agile, at any rate. Less clear that any of these steps are actually essential to quality.
There are teams who use a workflow that looks more like push-to-merge-queue -> if-tests-pass -> deploy-to-prod, and in my experience this results in significantly higher velocity (provided your e2e tests are actually sufficient to prevent outages).
But Quick and Dirty works very well in other environments.
A lot of it depends on whether you have a lot of customers and revenue you are putting at risk by making quick and dirty changes (mandates more process) or coming up with an MVP (quick and dirty might be beneficial if you can iterate faster).
Haha, no! Notice what's missing form that list? QA.