AgileWorks Romania
12Jun/17Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
12Jun/17Off

Intro to Test Driven Development Workshop

Dear Agile community members, you are invited to join a free workshop on TDD.

This workshop introduces participants to using test-driven development (TDD) to improve software design and overall quality of code. Participants will be introduced to TDD as a tool for achieving basic correctness, for learning design, and for exploring solutions to development problems.

The audience will be limited to 10 people, so please register early and make sure you free your spot if you can't come.


Please bring your laptop configured with a unit testing environment for the programming language of your choice. Make sure you have one failing test and one passing test.

Why attend

During this workshop you will learn and experience the following:

• Effective use of TDD to drive development
• The "red-green-refactor" cycle
• The 4 principles of simple design
• SOLID Principles (if time permits)
• Behavior slicing
• Hands-on TDD practice sessions 
• How to improve your TDD skills after leaving the class

Plenty of hands-on exercises are used to reinforce the concepts presented, allowing participants to try the new development techniques at first hand.

Agenda:

9:15 - 9:35   Welcome coffee & ice breakers

9:35 - 10:00  Intro and setting the stage for "Intro to TDD"

10:00 - 12:40  The "red-green-refactor" cycle & The 4 principles of simple design

12:40 - 14:00   Lunch

14:00 - 16:45   SOLID Principles & Behavior slicing

16:45 - 17:30   Recap & How to improve your TDD skills after leaving the class

Coffee breaks are available during the day.

Other info:


This is a free workshop. Lunch is sponsored by Mozaic Works. Make sure you register (by RSVP) as the places are limited.
Your host and trainer will be Alin Pandichi, software developer at MozaicLabs

Filed under: Comments Off
29May/17Off

Agile Talks {edition.next}

Hi,

Agile Talks wants to bring together people who are passionate about software development and agile methods.

We will have two talks of maximum 30 minutes and after that two Open Space slots for around one hours.

The event ends with a group retrospective and with some conclusions from the participants.

Agile Talks is a great opportunity to both learn from other people's experiences and discuss your own topics during the Open Space.

The talks are to be determined in the next period.

We are in discussions for the venue and will announce it soon.

If you want to sponsor Agile Talks, please get in touch. Participants love having some drinks and some food in the evening so that can discuss the current burning matters with more energy.

Agenda:

18:30 - 18:45 Arriving, socializing
18:45 - 19:00 Introduction
19:00 - 19:30 Talk 1 TBD
19:30 - 20:00 Talk 2 TBD
20:00 - 20:10 Break
20:10 - 21:00 Open Space - ask the speakers for more details or propose interesting topics
21:00 - 21:15 Retrospective, Closing

Filed under: Comments Off
29May/17Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
23May/17Off

Coding Dojo – Delete the implementation, keep the tests, reimplement

Let's take a simple open source library, delete the implementation,  keep the tests and try to re-implement the library following the tests. How is this any helpful? Well... It will teach us:
 - the "test first" mentality
 - developing an API from the user's perspective
 - evaluating if the existing tests are covering all the right corners 
 - identifying duplication and refactoring it out
 - expressing intent more clearly 
 - [you name it, after the event]

The open source library we are going to re-implement is written and tested in Javascript. You will need just a basic understanding of the Javascript language, nothing fancy.

See you there!

-----------------------------------------------------------

A Coding Dojo is a team practice format that accelerates knowledge transfer and sharing skills between team members. With an experienced facilitator, it is also a way of learning by applying various techniques.

Objectives

The following skills are typical candidates for improvement during a dojo:

• Refactoring
• Simple design
• Clean code
• Improving pair programming technique
• How to safely modify code you don't understand (usually legacy code)
• Learning a new programming language
• Unit testing
• Test driven development

In addition, coding dojo can be used by a team as a collective and structured way of solving difficult or risky problems related to production, like fixing a bug or redesigning parts of the application.

How it works?

The basic format of a coding dojo:

• All developers and the facilitator gather in a room.
• The facilitator introduces the purpose and the format of the coding dojo.
• One laptop with a functional development environment is connected to a projector.
• Two developers pair program on the laptop. The others are in the room, watching the code changes.
• Every 7 minutes, one developer leaves the laptop and the next one from the room takes his place.
• After a specified period of time (usually around two hours), the dojo ends with a retrospective.

Filed under: Comments Off
16May/17Off

Agile Talks #23

Hi,

You are invited to the last Agile Talks event of this season. New interesting topic will be presented. 

"Enhancing Clean Architecture - 2 n-dimensional layers" by Valentin Tudor Mocanu.

With this approach we can enhance the separation of concerns & capabilities offered by Clean/Lean Architecture: we want to easy respond to the changes, we want to be lean, we want a scalable and testable design, we want to easy change technologies. We need to fulfill what Uncle Bob expect from development: “stable productivity, inexpensive adaptability, extreme quality”. 

Valentin Tudor Mocanu currently acts as coach, consultant and trainer for various Agile methods (Disciplined Agile, XP, Scrum). He is Certified Disciplined Agile Coach & Instructor and Disciplined Agile Consortium Bronze Partner. In parallel, he is Process Coach/Project Manager at PSS Prosoft-Solution. Previously, he was involved in all kind of development activities, and develop software solutions for various target domains. He has built & provides team/organization guidance for clean code, refactoring, life-cycles, estimation, architecture and others. He blogs about agile/lean methods, principles, practices and about agile design. 

Agenda: 


18:45 - 19:00 Arriving, socializing
19:00 - 19:10 Introduction
19:10 - 19:45 Enhancing Clean Architecture - 2 n-dimensional layers
19:45 - 20:00 Break
20:00 - 20:50 Open Space - ask the speakers for more details or propose interesting topics
20:50 - 21:00 Closing

See you on 15th of June!

Filed under: Comments Off
15May/17Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
9May/17Off

Code & Beer Cluj

Let's get together to write good code and discuss interesting topics in IT.

Bring your laptop and your code or think about something that you would like to practice or discuss. There is NO pre-established agenda. It is up to you to come forth with ideas and make these meetings worth-while for you and the rest of the group.


Code & Beer is meant for people that want to learn and teach others.


We aim to create a "human knowledge-base" that will help each participant improve him/herself. It's important to actively contribute to these meetings with topics that you find interesting or puzzling. These could include: a technical problem that you encountered while working on your projects, an interesting article that you've read, a new technology/framework/language, TDD, coding best practices and patterns etc.

Be prepared to do some pair-programming. Don't be afraid to share your code and your opinions. It's the best way to learn and improve yourself.

The format:

(The schedule is not strict, what follows are just some guidelines to provide our meetings with some structure. You may arrive and leave at any time.)

The meetings last about 2 hours, starting from 7 p.m. Between 7.15 - 7.30 we have a very short introduction about the purpose of the meeting, the participants and what they want to practice. After that, we pair up and start coding and discussing.

If you decide to attend, please RSVP. This will help us determine the number of spots to reserve. When you know you cannot attend the meeting any more please change your RSVP to NO as soon as possible.

Filed under: Comments Off
1May/17Off

Code and beer

What

The code and beer idea is simple enough: we gather in the evening after work, in a pub, have a beer and write some code. It is a social coding event where you can share ideas with other developers. You can come and leave whenever you want.

Why would you come and join us

Meet other programmers
Work on your own project
Help others with their projects
Find someone who might help you with a specific topic
Pair with someone and learn new things
Just hang around and talk to people

How

Bring your laptop and some code that you'll be working on. If you don't have code then think about what you would like to practice during the evening.

There is no predefined agenda. We just meet and work on whatever we feel like.

Important

Please specify what you would like to do during the evening by answering the question "What would you like to practice?" when registering.

Also, as soon as you know you can no longer attend the meeting please change your RSVP to NO immediately. Consider this gesture a sign of respect towards other members of this group who might want to attend in your place.

The number of attendees is limited because of the difficulties of finding a big pub and making reservations for a big group.

Filed under: Comments Off
26Apr/17Off

Coding Dojo – The 9 rules of Object Calisthenics

Object Calisthenics are programming exercises, formalized as a set of 9 rules suggested by Jeff Bay in the book "The ThoughtWorks Anthology".


These rules focus on maintainability, readability, testability, and comprehensibility of your code. 


The rules are:

1. Only One Level Of Indentation Per Method
2. Don’t Use The ELSE Keyword
3. Wrap All Primitives And Strings
4. First Class Collections
5. One Dot Per Line
6. Don’t Abbreviate
7. Keep All Entities Small
8. No Classes With More Than Two Instance Variables
9. No Getters/Setters/Properties


We will refactor an existing codebase using only the 9 rules above.

-----------------------------------------------------------------------------

A Coding Dojo is a team practice format that accelerates knowledge transfer and sharing skills between team members. With an experienced facilitator, it is also a way of learning by applying various techniques.

Objectives

The following skills are typical candidates for improvement during a dojo:

• Refactoring
• Simple design
• Clean code
• Improving pair programming technique
• How to safely modify code you don't understand (usually legacy code)
• Learning a new programming language
• Unit testing
• Test driven development

In addition, coding dojo can be used by a team as a collective and structured way of solving difficult or risky problems related to production, like fixing a bug or redesigning parts of the application.

How it works?

The basic format of a coding dojo:

• All developers and the facilitator gather in a room.
• The facilitator introduces the purpose and the format of the coding dojo.
• One laptop with a functional development environment is connected to a projector.
• Two developers pair program on the laptop. The others are in the room, watching the code changes.
• Every 7 minutes, one developer leaves the laptop and the next one from the room takes his place.
• After a specified period of time (usually around two hours), the dojo ends with a retrospective.

Filed under: Comments Off