While pure TDD as defined by its canonical text can be frustrating and time consuming, simply not writing tests is not really a defensible position, and definitely not one that Go, or any other language, should attempt to make easier. Writing testable code, and writing tests, does not have to mean TDD. In my experience it always results in better code, and us tasty slower to write because you spend less time in dead ends. I've done my share of time restricted, stream of consciousness programming. The results are almost always unmaintainable. Saying you should write tests, and write code intending to be tested, is the right kind of virtue signalling. Tests are one of the few things we have that gives any meaning to words Software Engineer.
On Mon, 2 Mar 2020, 13:45 Warren Stephens, <wsteph...@prognoshealth.com> wrote: > Misha, > > Wonderful! This view is the furtherest away from mere TDD "virtue > signaling"! > > Warren > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/9e906437-f68f-4564-b7dc-1af31c4eb7cd%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/9e906437-f68f-4564-b7dc-1af31c4eb7cd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPGZSGKY49u8Ju2NyR_tj0oWVjHTgsnR%3DnJLt_k5GknK%2Beuaew%40mail.gmail.com.
