artodeto's free port

Date: 09.10.2012 Place: Mindsworks - Jarrestraße 42a, Hamburg Link: Meetup

new php usergroup page by Ole Michaelis Uses "github pages" and "jykil", Take a look on github.

how to defeat stage fright by Heiko Harthun Introduction www.heikoharthun.de www.arge-zeiten.de Heiko provides courses for developers to presentate themself as also the product on conventions/trade shows/exhibitions. He helps if the communication between developers and management (e.g. in the scrum retrospective) is not working anymore. general Only thing that helps against stage fright is moving around. It is also the only thing that helps effective. You should eat enough before you are going to present something. Try to eat energy rich things like nuts, bread, less sugar, things that contains L-Tyrosin and L-Tryptophan. body hack Autogenic training or meditation can help but they are helping after you have practised them for a long time (six months or more). Also going to sport (more the once per month ;-)) is helping to keep the level of adrenalin low. brain hack Try to create a solution/fallback for each problem that can occur. Things that can occur are "Questions inbetween", "fear for own existence", "nemesis in the crowd", "lose of the face", "blind spot", "blackout", "lose the thread" or "uninteded lauchter". The major answer is "what do i fear" and "why do i care to come into this situation". Try to have a fallback also for general problems (hardware is missing, hardware breaks down etc.). A solution can be, to listen on favorite music right before you start your presentation. source/books stryer - biochemie daniel pink was sie wirklich motiviert pruefungsangst - fortschritte in der psychotherapie

Compare notes about PHP UnitTest Workshop by Agata Raap and Frank Sons general Introduce unittesting in already existing and complicate to test source code is hard. Try to do a workshop by using already existing code to introduce into the topic "unittest". First write a unittest that covers know behaviors and after that, refactor the code. How can we test old code (with dependencies, strong coupling)? Keep current methods and exclude them into new methods. This new methods are testable by dependency injections or something similar. Always start and demonstrate unittest with simple examples. best practice (ask round) Getter setter testing? Code coverage - what does is tell? Is static code untestable? Should you test controllers?

This notes are a little bit late (yes i know ;-)) but free time is something that it is currently a kind of unreachable wish.