Venkat Subramaniam
Über Conf
Denver · June 14 - 17, 2010
Founder @ Agile Developer, Inc.
Dr. Venkat Subramaniam is an award-winning author, founder of Agile Developer, Inc., creator of agilelearner.com, and an instructional professor at the University of Houston.
He has trained and mentored thousands of software developers in the US, Canada, Europe, and Asia, and is a regularly-invited speaker at several international conferences. Venkat helps his clients effectively apply and succeed with sustainable agile practices on their software projects.
Venkat is a (co)author of multiple technical books, including the 2007 Jolt Productivity award winning book Practices of an Agile Developer. You can find a list of his books at agiledeveloper.com. You can reach him by email at venkats@agiledeveloper.com or on twitter at @venkat_s.
Presentations
Transforming to Groovy
Groovy is a elegant, dynamic, agile, OO language. I like to program in Groovy because it is fun and the code is concise and highly expressive. Writing code in a language is hardly about using its syntax, however. It is about using the right idioms. Come to this section to pick up some nice Groovy idioms.
Scala for Java Programmers
Scala is a very powerful, statically typed, hybrid functional, pure OO language.
The strengths of Scala is in its expressiveness, support for XML, powerful pattern
matching, and elegant solution to concurrency. In this workshop, you will deep dive
into understanding the strengths of Scala from a very practical point of view.
Scala for Java Programmers
Scala is a very powerful, statically typed, hybrid functional, pure OO language.
The strengths of Scala is in its expressiveness, support for XML, powerful pattern
matching, and elegant solution to concurrency. In this workshop, you will deep dive
into understanding the strengths of Scala from a very practical point of view.
TDD Regular Code/Multithreaded Code!
There are two reasons to do TDD. One is to ensure the code meets and continues to meet
the expectations at the unit of code level. The second, and equally significant, reason is to
drive the design of the code. Realizing the first benefit is rather mechanical and comes with rigor and discipline. Realizing the second benefit, however, requires quite some hard work and rethinking. It takes a bit of unlearning to achieve this goal.
TDD Regular Code/Multithreaded Code!
There are two reasons to do TDD. One is to ensure the code meets and continues to meet
the expectations at the unit of code level. The second, and equally significant, reason is to
drive the design of the code. Realizing the first benefit is rather mechanical and comes with rigor and discipline. Realizing the second benefit, however, requires quite some hard work and rethinking. It takes a bit of unlearning to achieve this goal.
How to Approach Refactoring
You can't be agile if your code sucks. You know that you have to constantly refactor your code and design. But the questions is how? In this presentation, instead of looking at a laundry list of refactoring techniques, we will instead look at how to effectively approach refactoring and along the way discuss some core principles to look for.