Jump to content

Eventos

  • entries
    145
  • comments
    0
  • views
    161,781

Contributors to this blog

  • jpaulino 121
  • Rui Carlos 13
  • staff 9
  • anolsi 1
  • apocsantos 1

1st Code Retreat Portugal 2012 (29 Setembro)


jpaulino

1,218 views

 Share

1st Code Retreat Portugal 2012

You know those guys that do yoga and they go on a trip into a secluded place and meditate? Yea, we can have that too.

How does it work?

The main objective of the code retreat is to improve software development quality through exercise and repetition. It's supposed to be a relaxed time and entirely out of scope in which the participants focus on writing perfect code rather than fast code.

The day will be split into 40 minute sessions, followed by a 10 minute retrospective. That will result in approximately 5 regular sessions throughout the day. An extra session will be held in a slightly different way, according to the audience's feedback.

The event will have room for a one hour lunch in which people will be able to discuss their progress in the experience. Also we will invite people to have an informal dinner (francesinhas anyone?).

There will be one or two facilitators. These people will poke around the participants' sessions and sensibly provoke their minds in order to better achieve code perfection and help them improve their skills.

At the end of the event, people will share their experience and their learning.

The four rules

The main focus of the event is to embrace TDD, good software design and pair programming techniques. The four rules of simple design are:

  1. Green tests — Always write one complete feature at a time with tests; make them green before moving on.
  2. No repetition — Keep things DRY. Elaborate on your design rather than just making it work.
  3. Expressive intent — Express yourself through code, make its intent as clear as possible.
  4. Low class and method count — Find the right balance between lots of classes / methods and expressiveness of your code.

The event is language agnostic as we encourage people to solve design problems rather than language problems. Object-oriented languages with a testing tool are more suitable to the challenge but you're free to pick any one you like.

I love it! What do I need?

Just bring your own laptop and snacks to eat along the journey. Bring a fair amount of snacks, you'll need them.

No fee is required to join us. Sign up by adding your name to the bottom of this page.

It's best to stick with the simplest and less distracting tools. If you're using a dynamic language like Ruby or Python or Javascript, a terminal is the best choice. If, however, you choose something like Java or C#, then an IDE will have to do. Remember, keep it simple, everyone should be able to understand the process.

1st Code Retreat Portugal 2012

You know those guys that do yoga and they go on a trip into a secluded place and meditate? Yea, we can have that too.

How does it work?

The main objective of the code retreat is to improve software development quality through exercise and repetition. It's supposed to be a relaxed time and entirely out of scope in which the participants focus on writing perfect code rather than fast code.

The day will be split into 40 minute sessions, followed by a 10 minute retrospective. That will result in approximately 5 regular sessions throughout the day. An extra session will be held in a slightly different way, according to the audience's feedback.

The event will have room for a one hour lunch in which people will be able to discuss their progress in the experience. Also we will invite people to have an informal dinner (francesinhas anyone?).

There will be one or two facilitators. These people will poke around the participants' sessions and sensibly provoke their minds in order to better achieve code perfection and help them improve their skills.

At the end of the event, people will share their experience and their learning.

The four rules

The main focus of the event is to embrace TDD, good software design and pair programming techniques. The four rules of simple design are:

  1. Green tests — Always write one complete feature at a time with tests; make them green before moving on.
  2. No repetition — Keep things DRY. Elaborate on your design rather than just making it work.
  3. Expressive intent — Express yourself through code, make its intent as clear as possible.
  4. Low class and method count — Find the right balance between lots of classes / methods and expressiveness of your code.

The event is language agnostic as we encourage people to solve design problems rather than language problems. Object-oriented languages with a testing tool are more suitable to the challenge but you're free to pick any one you like.

I love it! What do I need?

Just bring your own laptop and snacks to eat along the journey. Bring a fair amount of snacks, you'll need them.

No fee is required to join us. Sign up by adding your name to the bottom of this page.

It's best to stick with the simplest and less distracting tools. If you're using a dynamic language like Ruby or Python or Javascript, a terminal is the best choice. If, however, you choose something like Java or C#, then an IDE will have to do. Remember, keep it simple, everyone should be able to understand the process.

Mais Informações

 Share

0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site you accept our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.