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.

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:

Comments

Yet another interpretation of pyramid tests

In recent conversations regarding automating tests, It seems to me that the common understanding of the team is that the only acceptable automated test case is through the workflow tests through the UI. As far as I know, that’s not entirely correct and per “Pyramids of Automation” chapter 15 in More Agile Testing , I think there are lots of different ways we can automate test cases. I would like to take the opportunity to describe the pyramids of automation again with some thoughts/questions. First, let me try to describe the original pyramid again, and here’s the picture that is worth thousands of words Per the above pyramid from Mike Cohn with some modification in “More Agile Testing”, the lowest level, the unit tests, gets the fastest feedback on every commit which would provide the most benefits. The higher the tests located in the pyramid texts, the slower the feedback and lower profit we would get from the automated tests . “The test automation pyramid is a model intended to guid

Sudoku refactoring

Sudoku Refactoring Kata Following Jay and Llewellyn on their sudoku refactoring, I have forked the sudoku repo and added the java version. As usual, I will post the snippets I found useful in doing the refactoring Original repo: https://github.com/zoran-horvat/sudoku-kata our forked repo: https://github.com/calgarysoftwarecrafters/sudoku-kata Jay and Llewellyn attempt on this: https://github.com/JayBazuzi/sudoku-kata/branches , part 1: https://www.youtube.com/watch?v=BVGH-dNn-tc&ab_channel=LlewellynFalco , and you can follow other parts in the channel our C# refactoring attempt: https://github.com/calgarysoftwarecrafters/sudoku-kata/tree/tvo/sample-refactor-solution-steps our Java refactoring attempt: coming soon…. Snippets Golden Master Extract Method Extract anonymous class to named class Delete Comments convert parameters to object move the inner class to upper level specify type explicitly transform out parameters to object move types to matching files inline variable extract

What’s a simple way to share and learn refactor?

I have been organizing coderetreat and creating screencasts on refactoring and TDD, etc… however, I find it takes lots of time and effort to organize, preparing and facilitate. (it’s not that I complain about it as a matter of fact I love it every single second and I’m amazed at how much I have learned from the community) I have been asking myself, what’s the simpler way for me to learn to refactor and share with others? (why refactor, you may ask? it’s because it’s my favourite topic in the long never-ending list of agile technical practices) and for some reason, I really like to share my boring meme jokes, so I guess why not share a list of animated gifs of refactoring and the motivation of it. I guess since I’m an Asian guy (hopefully some kind of descendants from Bruce Lee) so this saying is pretty cool to me: “I fear not the man who has practiced 10,000 different kicks once, but I fear the man who has practiced one kick 10,000 times.” Another way to look at it, from J.B Rainsber

conversations on agile technical practices and investments

Search This Blog