I would think it's less traceable though, no? This is not coming from any industry knowledge, but I would think that an ATM would know the bill #s, so if you stole it, the bills would be tagged. You can always melt the gold. But this isn't based on any practical knowledge.
TDD is not dead, but hopefully the practise of foisting rigid, prescriptive, quasi-religious software development methodologies on creative individuals is.
TDD, like all of these things - eXtreme Programming, agile, has good points and bad. Listen to what these people have to say, and then take what works best for you.
To me, TDD is about writing my code and my tests at the same time, not test first. As soon as I write just enough code to do something, I'll write a test to see if it actually works. I'll then expand on that test and perhaps add a few more as I refactor that piece of code.
This means I still get the benefits of exploratory programming, unconstrained by test first, but I also get the security of knowing that my changes didn't break anything.
It feels very natural to develop this way, as the code base grows, your confidence in its quality grows with it, rather than the inverse (lots of passing tests). Also a fast test suite which runs on file save is addictive, I cannot imagine returning to F5 Driven Development now.
I can't state how much I dislike the quasi-religious part of TDD. Trying to establish a logical argument of trade-offs with someone who "believes" in TDD is from difficult to impossible.
The arguments always end up in line with "You just have to be better/be more confident/etc etc", or in more blunt term, "I'm better programmer than you, that's why TDD works for me but not for you".
> To me, TDD is about writing my code and my tests at the same time
This is exactly how I've taken up TDD. I still sometimes feel like I should write the tests first, but (and maybe this is just a matter of discipline) it's much more satisfying to do exactly what you described. The tests still help guide the design of the software, because it'll be immediately visible to me if I'm writing software that's hard to test (and probably - though not always - less correct).
> F5 Driven Development
This made me spit my drink out laughing; it sounds so ridiculous when you say it like that (because it is). You're right on the mark with the addictiveness of a fast, auto-refreshing test suite, I wouldn't want to go back to what feels like the caveman way to do things.
yes, the whole thing will break if JS is disabled or that script fails to load, but this is hardly a unique failing of TopLevel. Most websites will break under these circumstances these days.
agree about that sentence, really that's horrible. Replacing free water fountains with a private, paid alternative? The product itself is like a glimpse into some weird dystopia.
I don't think it is justifiable. Google's policies are a bandage for gaps in their algorithms, rather than fix their algorithms (admittedly, this is hard and it's not like they aren't trying) they have reached a point where they can use their monopoly power to dictate how websites act. They punish behaviour which hurts their main business - adwords.
I would expect an anti-trust case in the coming few years.