AgileWorks Romania
28Aug/17Off

Agile Talks #3

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.

First Talk: Robert Mălai  - "The Product Mindset". The Product Mindset will help your company to become a valuable partner to your customers, enabling them to fulfil their business goals. 

Robert is working as an Engineering Manager at 3Pillar Global. Robert is extremely passionate about technology and engineering, which he has been managing for the last 15 years in various teams. He has built products from embedded software development in automotive to distributed services in the cloud. Robert is also passionate about databases, Linux servers, Python, JavaScript and Software Development. Prior to joining 3Pillar, Robert was involved in the automotive industry during his stint at Continental Automotive.


Second Talk: Iulian Paduraru - Facilitation - What actually is it?. During this session Iulian Paduraru will share his thoughts on what facilitation is and how can we use it in our company so that we overcome our obstacles.


Iulian is an Agile Project Manager and Agile Coach at isoftbet.com. With a background as a software developer, he is very passionate about agile, software development and technology in general.

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 Robert Mălai - "The Product Mindset"
19:30 - 20:00 Iulian Paduraru - "Facilitation - What actually is it?"
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
22Aug/17Off

Coding Dojo

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
21Aug/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
7Aug/17Off

Spark v2.2 Workshop

This 4-hour training course introduces Apache Spark v2.2, the open-source cluster computing framework with in-memory processing that makes analytics applications up to 100 times faster compared to technologies in wide deployment today. Highly versatile in many environments, and with a strong foundation in functional programming, Spark is known for its ease of use in creating exploratory code that scales up to production-grade quality relatively quickly (REPL driven development).

The main focus will be on what is new in Spark v2.2 and this includes DataSets (compile-time type-safe DataFrames), Structured Streaming, as well as the de-emphasizing of RDDs.

The plan is to follow the agenda below but if participants want to dive deeper into high-complexity topics I will instead focus on live coding ad-hoc demos.

1. The first part of the workshop covers Spark SQL with Scala, specifically the limited toy examples emphasized by Spark documentation and tutorials. Spark SQL, used in isolation, can realistically only be used for such didactic use cases. As a practitioner I know from experience that when ingesting real-world datasets, Spark SQL will very quickly show its limitations and therefore some more powerful techniques are needed.


2. The second part of the workshop covers these techniques without which Spark SQL is largely ineffective. This section of the workshop is about sharing lessons learned the hard way, and experience gathered in the trenches of the real world.

3. The third part of the workshop, titled "Machine Learning By Example", covers multiclass classification using SparkML's Pipeline API with Scala. SparkML is the machine learning module that ships with Spark.

4. During the remaining time, we'll focus on a Scala / Spark Streaming application that ingests data from Apache Kafka (an open-source, high-performance, distributed message queue), performs streaming analytics, then saves the analytics results back into Kafka.

All examples will be in Scala.

Please bring your laptop with you.

The workshop is free of charge and seating is first-come-first-serve.


The workshop has some requirements. Please consider the following:
1. Bring your own laptop.
2. Have Docker already installed before the workshop.
3. Have the Docker image already pulled and available locally.
Here are the necessary instructions (prefix these commands with sudo if required):
2. Install Docker
Ubuntu: apt-get -y install docker.io
CentOS: yum -y install docker
Linux / Other: curl -fsSL https://get.docker.com/ | sh
Mac and Windows: https://www.docker.com/products/docker-toolbox
3. docker pull dserban/dockersparknotebook

Filed under: Comments Off
7Aug/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
31Jul/17Off

Agile Talks #4

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.

First Talk : Andreea Grigoras -  "Adapt the system to the people, and not the people to the system" . It is a story about a scrum master who, together with her team, discovered what it really means to be agile. They failed, they have experimented and kept on trying, until they found their way of doing things.

Andreea is a Scrum Master at 123ContactForm, and is constantly trying to help product teams be better, faster, acting like a single organism. She likes to work with people and learn new things with every occasion she's got. You can usually find her running through the desks from one person to another while answering and asking questions, or complaining she hasn't read a book in days. 

https://www.youtube.com/watch?v=0Een-GhdriU

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  Andreea Grigoras - "Adapt the system to the people, and not the people to the system"
19:30 - 20:00 Talk 2
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
25Jul/17Off

Coding Dojo – Let’s do TDD on Minesweeper

During this edition of the Coding Dojo, we are going to apply test driven development to develop the well-known Minesweeper game. To quote Wikipedia: "The objective of the game is to clear a rectangular board containing hidden "mines" or bombs without detonating any of them, with help from clues about the number of neighboring mines in each field."

Until then, here is a online version of the game to keep you busy: minesweeperonline.com

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

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
25Jul/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
10Jul/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
27Jun/17Off

Coding Dojo – Strong-style pair programming

Traditional pair programming might have some drawbacks: the pairing partner can't keep up, they get bored and disengaged, the driver is hogging the keyboard, etc. An alternative style of pair programming can fix all these problems. We'll try this alternative during this coding dojo meetup: the strong-style pair programming.

The golden rule for this style of pairing is:
"For an idea to go from your head into the computer it MUST go through someone else's hands"


Instead of "I have an idea, give me the keyboard", we'll try to do things the other way around: "I have an idea, please take the keyboard"

Many thanks to Llewellyn Falco for proposing the alternative of strong-style pair programming! Read more about it on his blog: http://llewellynfalco.blogspot.ro/2014/06/llewellyns-strong-style-pairing.html

See you at the meetup!

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

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