In the last couple of weeks we’ve asked each speaker to answer five simple questions (a.k.a 5Whys) and got some interesting results:
- Angel Medinilla's answers
Session: Unicorns, Krakens, Self Organizing teams and other mythological beasts - Gil Zilberfeld's answers
Session: To Estimate Or #NoEstimate, That Is The Question - Ilan Kirchenbaum's answers
Session: If agile is such fun, why is there a queue at the HR office? - Eyal Golan's answers
Session: Working with Legacy Code – This Is Reality - Noam Zweig's answers
Session: Managing technical debt in Cyberark – our way of doing it
Why should people come to the conference?
It is a great opportunity to meet other professionals who are passionate about being agile and want to learn more. In the past I had interesting conversations with conference attendees and learnt quite a lot.Why should people come to my session?
To learn about TDD :)If you want to add another great design methodology to your tool belt - this is the session you need to hear.
It doesn't matter if you tried TDD in the past or just beginning with unit testing.
Why did I choose the topic?
There have been quite a lot of misunderstanding in this field and although it seems as if TDD exist since the beginning of time it is still misunderstood and misused.I hate to see software developers avoid this practice due to bad experience and lack of understanding of how it works and so I've decided to create a session that shows TDD with a "real" application - not just a trivial example.
No comments:
Post a Comment