How to write Clean, Testable code. Google NYC meetup

Testing is not like frosting

Just attended wonderful meet up in New York Google office dedicated testing. Extremely smart guy Miko, Google Engineer, gave a great talk summarizing the main concepts behind testing and TDD. Moreover he touched psychological aspects of testing, which are in my opinion even more important than technical. Everything in 30 slides, we all new these but never realize and never do.





Started from how to write hard testing code:
- singletons and static methods (I've got some points for this)
- put a lot of new operators
- code complexity and violating of Demeter Law.
...
If you know how to create unreadable code you probably know how to fix it?

Moreover he touched such a topic as creating tests from spec and BDD:

@Test public void itShouldCloseTheIncomingConnectionAlways()

I liked an amazing classifications of bugs into 3 categories as logical, wiring and rendering bugs. And finding super bug is just misunderstood of the concept.

Just read the presentation: How to write Clean, Testable code: Psychology of Testing

Misko blog: is misko.hevery.com
And do attend NYC Google meetup, don't miss a chance to visit awesome office and great people