There were a lot of great meetups in 2011 and we talked about so many topics. But there are still enough left for 2012. So we will come together again in January.
Our first topic in the year 2012 is 'Self-management and Getting Things Done'. This is a perfect start for all of us, who have some New Year's resolutions to be done.
We will get together at tarent's office about 19:00 on 16. January 2012.
You can sign up for the event on Xing here.
Dienstag, 20. Dezember 2011
Donnerstag, 24. November 2011
Post-meetup: November 2011
We broke some records for our November Meetup. Eighteen people showed up, and we had a great time watching the first three of Uncle Bob's CleanCode videos.
Michael Hüttermann wrote a great recap of the evening on Google Plus. And beyond that there's not much to say other than a big thanks to Doo.net for sponsoring us with the licenses, and Viaboxx for the room, candy and drinks!
And thanks to Stefan Walter for the pic!
Note that we'll skip the Meetup in December. So the next meetup will be January next year. Until then, guten Rutsch!
Montag, 31. Oktober 2011
Bonn Agile Meetup - November 2011: Clean Code Videos
Doo GmbH has been kind enough to sponsor the Meetup with community licenses for the first CleanCoders.com episodes (by Uncle Bob)!
We'll get together and view them in Viaboxx' offices (where we had the Sommerfest), discuss the contents, and if it turns out popular, we'll do more events like this in the future.
The agenda is discussed here: https://groups.google.com/d/topic/bonnagile/i1h2hO9YhIA/discussion
Sign up for the Xing event here: https://www.xing.com/events/bonn-agile-meetup-november-831617
Note that if you want to catch the introductory CleanCoders Episode 1, you'll have to show up half an hour early. We start with Epsiode 2 at 19:10'ish. You can also watch Episode 1 in advance at home or wherever, as it only costs 1$.
We'll get together and view them in Viaboxx' offices (where we had the Sommerfest), discuss the contents, and if it turns out popular, we'll do more events like this in the future.
The agenda is discussed here: https://groups.google.com/d/topic/bonnagile/i1h2hO9YhIA/discussion
Sign up for the Xing event here: https://www.xing.com/events/bonn-agile-meetup-november-831617
Note that if you want to catch the introductory CleanCoders Episode 1, you'll have to show up half an hour early. We start with Epsiode 2 at 19:10'ish. You can also watch Episode 1 in advance at home or wherever, as it only costs 1$.
Dienstag, 18. Oktober 2011
Post Meetup: October 2011 (Code Reviews)
Just a quick recap from yesterday's meetup:
Twelve agilists met up in Tarent's awesome kitchen/meeting area, where we were welcomed with sweets, snacks and drinks. Thanks again for hosting us! I did a (somewhat shaky) demonstration of Gerrit, and then we had a long discussion on how to apply Code Reviews as an (agile) practice. We filled up a couple of whiteboards with notes:
(If you can read any of that, I apologize for my lousy German spelling). Here are some of the keywords:
We started by discussing what can make code review successful, or what makes people happy about it. Security was mentioned. Motivation (someone will actually look at the wonderful code I've produced!). It has to be self-driven from the team, not forced from above. Consensus on the quality of the code. You need to have a critical mass of people engaged in doing reviews. Don't allow the reviews to become a bottle neck. Face-to-face reviews are great, but code review is perhaps even more necessary in distributed teams (but then you need to write really good commit messages!).
How can we do code reviews?
General/lieutenant scheme might work well in open source projects, but no so much in companies. The co,mitter should invite a reviewer (anyone got a sec to review this bit of code?). Don't nail it down into processes and roles . Don't leave the reviewing to seniors, mix and match. Reviewing is a learning process.
Code reviews might be a practice that is initially easy to get accepted, politically and culturally, compared to pair-programming. If introducing pairing is not working for you, maybe code reviews will work. If you are doing pairing, maybe reviews aren't necessary (although they can have a good effect in bringing in a fresh pair of eyes, more objective view on the code).
Perhaps pair programming is more useful in creative development. When doing maintenance, perhaps code reviews are better suited.
We're collecting related interesting links in this thread on the mailing list. I also started a discussion on Google+ about code reviews, that got quite active, but unfortunately I didn't mark it as Public, and therefore I can't get it out there now. I did however copy it into another mail thread. Feel free to keep on discussing in that thread!
Looking forward to the next meetup! Any ideas for topics are welcome (in the mailing list).
Twelve agilists met up in Tarent's awesome kitchen/meeting area, where we were welcomed with sweets, snacks and drinks. Thanks again for hosting us! I did a (somewhat shaky) demonstration of Gerrit, and then we had a long discussion on how to apply Code Reviews as an (agile) practice. We filled up a couple of whiteboards with notes:
(If you can read any of that, I apologize for my lousy German spelling). Here are some of the keywords:
We started by discussing what can make code review successful, or what makes people happy about it. Security was mentioned. Motivation (someone will actually look at the wonderful code I've produced!). It has to be self-driven from the team, not forced from above. Consensus on the quality of the code. You need to have a critical mass of people engaged in doing reviews. Don't allow the reviews to become a bottle neck. Face-to-face reviews are great, but code review is perhaps even more necessary in distributed teams (but then you need to write really good commit messages!).
How can we do code reviews?
General/lieutenant scheme might work well in open source projects, but no so much in companies. The co,mitter should invite a reviewer (anyone got a sec to review this bit of code?). Don't nail it down into processes and roles . Don't leave the reviewing to seniors, mix and match. Reviewing is a learning process.
Code reviews might be a practice that is initially easy to get accepted, politically and culturally, compared to pair-programming. If introducing pairing is not working for you, maybe code reviews will work. If you are doing pairing, maybe reviews aren't necessary (although they can have a good effect in bringing in a fresh pair of eyes, more objective view on the code).
Perhaps pair programming is more useful in creative development. When doing maintenance, perhaps code reviews are better suited.
We're collecting related interesting links in this thread on the mailing list. I also started a discussion on Google+ about code reviews, that got quite active, but unfortunately I didn't mark it as Public, and therefore I can't get it out there now. I did however copy it into another mail thread. Feel free to keep on discussing in that thread!
Looking forward to the next meetup! Any ideas for topics are welcome (in the mailing list).
Mittwoch, 12. Oktober 2011
Bonn Agile Meetup - October 2011: GTD, Code Review/Gerrit
The next Bonn Agile Meetup will take place on the 17th of October, again in the lovely Bierhaus Machold at 19:00 in Tarent's offices in Bonn/Duisdorf (map updated below).
View Larger Map
Topics might include:
View Larger Map
Topics might include:
- Code review (with Gerrit demo)
- Getting Things Done (GTD)
Sign up for the Xing event, and help plan out the agenda on the mailing list below:
Hope to see you there!
Montag, 12. September 2011
Werwölfe in Bonn - (Sept. meetUp)
Am 19.09. um 19:00 findet das September meetUp statt.
Ort und Anmeldung findet Ihr hier: https://www.xing.com/events/bonn-agile-meetup-september-811871
Diesmal wird Kurt Häusler von den Events:
Ort und Anmeldung findet Ihr hier: https://www.xing.com/events/bonn-agile-meetup-september-811871
Diesmal wird Kurt Häusler von den Events:
berichten.
Und wir werden bei einem Spiel "Werwölfe" jagen.
Was das mit agile zu tun hat? Lasst euch überraschen!
Donnerstag, 18. August 2011
Bonn Agile Sommerfest die II.
Nach 6 Meetups mit zusammen 45 Teilnehmern, fand am letzten Montag das Bonn Agile Sommerfest statt.
Bei gutem Wetter waren wir von der Firma Viaboxx zu einem BBQ eingeladen.
Neben tollen Gesprächen, lecker Essen und kühlen Drinks gab es auch wieder eine vorbereitete Präsentation.
Thomas zeigte uns das "Roman Numerals" Kata implementiert in Clojure.
Natürlich blieb auch genug Gelegenheit sich über die agilen Arbeitsweisen von Viaboxx zu informieren oder den vorhandenen Kicker zu nutzen.
Bei gutem Wetter waren wir von der Firma Viaboxx zu einem BBQ eingeladen.
Neben tollen Gesprächen, lecker Essen und kühlen Drinks gab es auch wieder eine vorbereitete Präsentation.
Thomas zeigte uns das "Roman Numerals" Kata implementiert in Clojure.
 |
| Roman Numerals Kata |
Abonnieren
Kommentare (Atom)