Well, just need to find a FireWire cable and test :) Kind of want to see this thing with my own eyes :)
Would love to see a demo if you end up doing this.
Nasty phishing attack leveraging the browser fullscreen API.
It’s clever, though kind of obvious on my laptop. I run Linux and the window borders are different once in fullscreen (different shape and color).
This seems more like, “tests are good” rather than “TDD is good”. Also, the “Show Lobsters” is a little misleading. I expected to be linked to a project, not a blog post.
Code Complete 2 has some good statistics on how useful testing can be, done in several larger studies over large codebases that is worth looking into. I think that testing is fairly uncontroversial now, although TDD is still controversial. Although reducing how frequently you generate bugs is clearly good, I think that the best part of having tests is that it lets you refactor with confidence (I am stealing this phrase from someone, I forget whom). If you make a big change and you have good test coverage, you can be reasonably certain that the refactor was not a step backward in terms of correctness.
I would be more interested in seeing a comparison between “test first” and “clearly define API first, test whenever”.
I thought the “Show Lobsters” was supposed to be used when sharing my own blog post. I just removed it.
Anyway, thanks for the feedback :) I haven’t read Code Complete 2, I’ll make sure to check it out. I think we are on the same page about the benefit of TDD. I definitely love fearless refactoring. As for testing or TDD adoption, I would agree that it is not controversial in the web community (I work with PHP, JS and Ruby; each of these community are believing in the importance of testing). However, I work with a lot of non-web folks who sadly are skeptical about the benefit of automated testing :(
I had the same question. Good to know the answer.
Proposed tag: performance
For any performance related topic.