I'm a very straightforward data science student in last year before master graduation. I like to learn bottom-up step by step and go through the logical discovery process myself as much as possible
I'm currently a data-science student and have been practicing this methodology for my life until I realised that all I was doing was: doing too fast, pattern matching, hacking my way to solutions, missing tons of important elements. What I learnt is that not taking the time to do things correctly adds up until you're totally lost, it be in your code, in your studies or in your work. I get the principles and see how this kind of stimulations allowed me to think fast for all these years, but I also totally see how it traduce in the industry in bad coding practice/documentation, not well thought code etc. I would say you can apply this principles in R&D but other field have probably more to gain with TDD overall, unless you're keen to repeating mistakes over and over
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 currently a data-science student and have been practicing this methodology for my life until I realised that all I was doing was: doing too fast, pattern matching, hacking my way to solutions, missing tons of important elements. What I learnt is that not taking the time to do things correctly adds up until you're totally lost, it be in your code, in your studies or in your work. I get the principles and see how this kind of stimulations allowed me to think fast for all these years, but I also totally see how it traduce in the industry in bad coding practice/documentation, not well thought code etc. I would say you can apply this principles in R&D but other field have probably more to gain with TDD overall, unless you're keen to repeating mistakes over and over