@tsoding Well, both are bad. Good code is modular, if what you copied and pasted in, can be tested in isolation, it's fine. The problem is never where did it come from. It's, are you hamstrung by it, does it screw you and the team?
Yes indeed, Marcel, please consider NOT stepping on product namespace. Obviously you're along the road a ways in product delivery and promotion... https://t.co/ZVNkCmoBo9 is significantly further along that same journey. So display all your empathy and awareness and do right.
@_wilfredh Then also to trick yourself into abandoning the blogging engine and the blogging... until you do the same thing again. It's the digital equivalent of buying a notebook.
Seems to me, the real truth about TDD is that your code is going to be hard to test if you don't at least think about how you'd test it first. At which point, you should write a test, then you'll find out (many of) the other things you didn't think of too.