It's not that you shouldn't test private methods, it's that you should write code in which private methods don't need to be tested.
Anything taken to extremes is unproductive. Including criticism of methodologies based on their philosophies being taken to extremes, usually out of context. Which I find happens with TDD a lot.
Of course! I totally agree here, but I also think that we speak too often in absolutes and ignore the nuance that day-to-day coding requires. Arguments like these are sometimes easier said than done.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.