Since these presentations were spare time hobby - I've decided to share them :) Hopefully someone will find them useful. This part is about Eclipse plugin Mylyn - Task focused development environment.

2. Adapter

3. Decorator

4. Chain of responsibility

5. Design PuzzleMini seminār #1 followup

6. Application: Email spam filtering system. Both HTML and Text formats should be supported. Multiple spam recognition algorithms are present and several could be used simultaneously. Multiple weekly report approaches should be supported: XML, HTML files on filesystem;+ email  with report attachment. Mini seminar #1:Pattern puzzle

7. Pick up to 2-3 design patterns to review next time Question to audience

9. Best practices: Mylyn & Atlassian connectors(Mini Seminar #2) Leonid M.

11. Practices: Brainstorming

13. Brainstorming: Values?

14. Brainstorming: Practices?

18. Task context is linked to the issue

19. Code comments are resolved to tasksMeasures (worklog) - “Real work” measures are provided Traceability #1

20. Traceability #2

21. Traceability#3: Worklog

23. Reviewing SVN history is unnecessary effort

24. We want to see that was in mind (the whole context)

25. Isn’t the code review issue-oriented? Information & Expertise sharing#1

26. Information & Expertise sharing#2 Why not to review Mylyn issue context instead?

27. AIR & Bamboo Build from your IDE See build status Navigate to the roots of the tests failure

28. Gotohttp://www.infoq.com/presentations/mik-kersten-eclipse-mylin-tfi Still not persuasive?

29. Questions