I'm talking from real world experience... so I don't think that calling me a developer who doesn't care or know better is particularly helpful here.
Take bug fixing for example. Someone finds a bug & raises a ticket. First step is to confirm how the system SHOULD work in that scenario. Oftentimes that's obvious, sometimes it needs a chat with a BA/stakeholder.
That done, I write a test for how the system SHOULD work, and the test clearly fails. Then I fix the bug, and the test passes.... TDD in action.
New feature development is completely different. Spike research is another area that would be impossible for TDD.
As a developer, I try to always use the appropriate tools at the appropriate time. TDD has its uses, but it isn't a panacea.
I am a self-taught developer from Argentina currently living in Spain. I am passionate about improving my technical skills and helping others do the same.
Don't worry, and please, don't delete anything on my account (I already see deleted messages in the thread).
Given your name, and the content of the TDD article, it's clear that while your English is good, it's not your first language (I'd guess you're Italian, and while I get by in written & spoken Italian, trust me, your English is better than my Italian).
In the spirit that I believe Dev.to was started, the debate is a good one to have - and with any good debate, there will be differing opinions.
I am a self-taught developer from Argentina currently living in Spain. I am passionate about improving my technical skills and helping others do the same.
Argentinian, but yeah Italian parent ahah. Yeah also I am not into deleting conversation but that message didn't gave anything to the argument, I felt it was just noise since you answered that in other answers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm talking from real world experience... so I don't think that calling me a developer who doesn't care or know better is particularly helpful here.
Take bug fixing for example. Someone finds a bug & raises a ticket. First step is to confirm how the system SHOULD work in that scenario. Oftentimes that's obvious, sometimes it needs a chat with a BA/stakeholder.
That done, I write a test for how the system SHOULD work, and the test clearly fails. Then I fix the bug, and the test passes.... TDD in action.
New feature development is completely different. Spike research is another area that would be impossible for TDD.
As a developer, I try to always use the appropriate tools at the appropriate time. TDD has its uses, but it isn't a panacea.
I really need to check my words before answering as again I didn't not meant anything I said as an attack onto you.
Don't worry, and please, don't delete anything on my account (I already see deleted messages in the thread).
Given your name, and the content of the TDD article, it's clear that while your English is good, it's not your first language (I'd guess you're Italian, and while I get by in written & spoken Italian, trust me, your English is better than my Italian).
In the spirit that I believe Dev.to was started, the debate is a good one to have - and with any good debate, there will be differing opinions.
Argentinian, but yeah Italian parent ahah. Yeah also I am not into deleting conversation but that message didn't gave anything to the argument, I felt it was just noise since you answered that in other answers.