ECOOP /
Birds-of-a-Feather (BOF):
The Code-In and Refactoring Party: Play Teacher and Student
Building S1/01
Karolinenplatz 5
64289 Darmstadt
Wednesday, July 23
Somewhat in the spirit of the annual Camp Smalltalk at OOPSLA, the Code-In is a communal BOF event to share our love and fun with programming and tools. In essence, the Code-In involves developers pair programming, sharing their skills and tools.
Developers like to socialize around programming and tools, and the Code-In is a hands-on place to do that.
In addition to participating as a student, the Code-In is a place where you may play the role of a coach; teaching another interested developer about something or some tool that would like to share. We’re all potential coaches and students at the Code-In.
In addition to any and all playing the role of coach at the Code-In, we’ll be working to invite various thought-leaders that may be attending the conference to play the role of coach in methods such as refactoring, test-first programming, code reviews, and tools and languages, but no promises on who will show up.
Rules of the Game
We can play all three roles at the party. Anyone may be a coach; anyone a student. In each, humor and gentleness is appreciated. So is beer. This is fun with computers, not serious stuff.
- Method-Oriented Coach - for example, let’s pair program for 30 minutes while I coach you in how to refactor (using the code you brought on your laptop), or in test-first programming with JUnit.
- Technology-Oriented Coach - for example, let’s pair program while I coach you in AOP using AspectJ, or applying the refactoring features in the Eclipse IDE.
- Student - to a coach; usually does the hands-on typing.
Coach-Student games involve pair programming, usually with the Student at the keyboard—not the Coach, with the exception of code review games, or when otherwise appropriate. Coaches will have signs at their tables advertising what they can coach.
Equipment
If you are coaching, please bring your laptop, and tools and samples set up for ease of learning.
There will be tables, chairs, and power outlets.
If you would like to learn more about refactoring or have a code review, please bring your laptop and your code.
Refreshments: The Code-In is a parsimonious party, so you may need to bring your own beer. I’ll see if I can find a case to bring along, but no promises…
Examples
Share or learn what intrigues you: Refactoring, test-first programming, code review to polish Java, the new 1.4 java.nio library, ASP.NET, a performance analysis tool, XUnit, C#, AspectJ, Ruby, Python, XEmacs, Eclipse, creating a web service with .NET tools, …
Expectations
Some Code-Ins have 5 people; some have 25. It’s always a surprise.
Facilitators
Craig Larman - Craig will volunteer as a coach for at least AOP with AspectJ. He would like to be a student of many things. Craig is the author of Applying UML and Patterns, and the Java 2 Performance and Idiom Guide.
|
top
