And here’s Uncle Bob again (I want you for the TDD armee!), episode 99.000:
http://blog.cleancoder.com/uncle-bob/2017/03/03/TDD-Harms-Architecture.html
Discussions about episode 99.000 are easy to find with google for those interested.
For those not having read a former thread: BDD / TDD criticized
Moreover, on guru-driven (Uncle Bob is one of the gurus I find) agile development:
We observe a rising scepticism towards Agile Methods:
practitioners are not able to use them in an efficient and
effective way since the underlying assumptions are hidden
by gurus. This missing knowledge is furthermore used by
agile zealots to indeed legitimize hacker behaviour. The
reputation of Agile is at stake.
To avoid that Agile Methods become obsolete, we think
it is necessary to understand software development process
tactics, i.e., knowledge about when to use which practice,
knowing its advantages, its disadvantages, and how to
apply it.
Therefore, we propose the use an approach to collect
falsifiable knowledge about agile methods, for example
using the Quality Improvement Paradigm.
To change this attitude, i.e., to switch from believing a
guru to adopt a scientific approach requires educational,
cultural, and managerial changes. To study how to accomplish
these, will be the challenge of the future.
(http://darkagilemanifesto.org/dark-side-of-agile-janes-succi-splash-2012.pdf)
Moreover Lamport:
TDD is useful mostly because it makes you think before you implement. Tests are
"a piss-poor way of trying to specify something." (certainly hard algorithms)
