Skip to main content

Collaborative Learning at Coderetreats


Written collaboratively by:

Trung Vo, Bob Allen, Jacqueline Bilston, Christopher Fietz, Llewellyn Falco

“… I really liked that there was something there for every level and anytime I would get stuck, there was someone there to help….” — Sara K.

What is a Coderetreat?

Coderetreat is a day dedicated to allowing developers time to practice their craft. The focus is on practicing skills like Test-Driven Development (TDD), refactoring, and incremental design that is proven to make developers move faster with fewer bugs. It is designed to enable participants to focus on their practice, with as few distractions as possible.

The day is made up of several short sessions where we either work in pairs or mobs to solve a small coding problem. Each session, we start new with the same problem; this allows us to focus on the new skill we are learning.

pair up, code, reset, repeat

What do you get out of it?

Coderetreat is an excellent place to learn what you know and what you don’t know. As in life in general, there are always new people to meet, new things to learn, and new ways of working and playing together, whether it be with code or ideas. They create a space where we can try out things that we have always wanted to try out, but we’ve never had time to try. Coderetreat is about peer learning, it can be hard to step outside of your comfort zone but together with other people, it is easy and even fun.

It’s easy to mean to practice. You’ve probably been meaning to practice already. Meeting together gives you a chance to actually do it. When we work in a pair or group, we are able to exchange new approaches and ideas and keep each other honest about actually using best practices.

Where can I find one?

Check out the Coderetreat website for one near you. Every November there is a Global Day of Coderetreat with sessions all over the world, on the same day.

Here are two online events that are coming up soon:

What is a code retreat animated text


Labels:

Comments

Post a Comment

Popular posts from this blog

growing object oriented software, guided by tests summary

Key ideas practice TDD as a design technique and not as a testing technique Software development as a learning process. Expose uncertainly early by testing our assumption as early as possible we use mock objects to identify the essential interactions between modules/objects. This leads to more effective abstractions, which reduces the cost of changing the cost safely over time. Stub queries; expect actions??? Write code that depends as little as possible on its context. programming by intention Test-Driven Development (TDD) and Quality Software development as a learning process. The best approach a team can take is to use empirical feedback to learn about the system and its use and then apply it back to the system. Development is incremental and iterative. Incremental development builds a system feature by feature. Each feature is implemented as an end-to-end slice. As a result, the system is continuously integrated and ready for deployment. A system is deployable when the acceptance t...
Post a Comment
Read more

Code Retreat 2017 retrospective

  In general, this year is much better compared to previous years There are several important points that I need to write down Typically, the main reason for me to do code retreat to help developers in the community to expose more to TDD/craftsmanship. Recently, I asked myself question: “How come it’s not eas y  to adapt TDD, automated testing which should be the core value of any efficient teams?” I don’t think that people is lazy or people is resistance, I think as the industry, there’s lots of ambiguity in how people should approach TDD (SOLID principles, 4 simple rules of design, etc … are too generic) and agile practices (agile manifesto, etc…) How can I apply SOLID, 4 simple rules of design into my day to day jobs? What’s the most important reasons for developers to write automated tests? is it testability design, is it executable documentations?…. what’s the different between integration/component/API tests? should we care? when I discuss about unit tests with QA, typic...
Post a Comment
Read more