It sounds like releasing daily is part of your testing strategy in that you simply let your customers do the testing for you.
Making small incremental changes with extensive manual testing can work. It just looks like you don't have to pay for the test effort.
I've seen it a fair bit with internal projects at larger companies but most external customers I have met in my career would quickly switch products.
Edit: It also sounds like you are confusing best practices with good code. I've met teams, usually without a formal cs education, who haven't used version control and didn't have any unit tests, but still had a well designed codebase. Of course best practices are best practices for a reason....
> Edit: It also sounds like you are confusing best practices with good code. I've met teams, usually without a formal cs education, who haven't used version control and didn't have any unit tests, but still had a well designed codebase. Of course best practices are best practices for a reason....
1) They both have degrees in comp sci.
2) For very narrow definitions of the word "good" you would be correct. Its technically functional and reliable. However, it regularly has problems with security and/or changes to the common library breaking other people's services.
Making small incremental changes with extensive manual testing can work. It just looks like you don't have to pay for the test effort.
I've seen it a fair bit with internal projects at larger companies but most external customers I have met in my career would quickly switch products.
Edit: It also sounds like you are confusing best practices with good code. I've met teams, usually without a formal cs education, who haven't used version control and didn't have any unit tests, but still had a well designed codebase. Of course best practices are best practices for a reason....