Design Patterns<br /><ul><li>Strategy
Adapter
Decorator
Chain of responsibility
Design Puzzle</li></ul>Mini seminār #1 followup<br />
Application: Email spam filtering system. Both HTML and Text formats should be supported.<br />Multiple spam recognition a...
Pick up to 2-3 design patterns to review next time<br />Question to audience<br />
Best practices: Mylyn & Atlassian connectors(Mini Seminar #2)<br />Leonid M.<br />
Development process<br /><ul><li>Values & Principles: Brainstorming?
Practices: Brainstorming
ESWIJI project on the map</li></ul>Mylyn<br /><ul><li>Tying it all together (in context if ESWIJI project)</li></ul>Mini s...
Brainstorming: Values?<br />
Brainstorming: Practices?<br />
ESWIJI project on the map<br /><ul><li>Use tools not brains
Easify & Delegate </li></li></ul><li>Mylyn<br />
Code change – is change request <br />- Mylyn enables task focused interface, coding against a task is a MUST<br />Bug tra...
Task context is linked to the issue
Upcoming SlideShare
Loading in …5
×

3. Mini seminar 2 - Mylyn

763 views
732 views

Published on

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.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
763
On SlideShare
0
From Embeds
0
Number of Embeds
69
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • http://www.infoq.com/presentations/mik-kersten-eclipse-mylin-tfi
  • 3. Mini seminar 2 - Mylyn

    1. 1. Design Patterns<br /><ul><li>Strategy
    2. 2. Adapter
    3. 3. Decorator
    4. 4. Chain of responsibility
    5. 5. Design Puzzle</li></ul>Mini seminār #1 followup<br />
    6. 6. Application: Email spam filtering system. Both HTML and Text formats should be supported.<br />Multiple spam recognition algorithms are present and several could be used simultaneously.<br />Multiple weekly report approaches should be supported: XML, HTML files on filesystem;+ email  with report attachment.<br />Mini seminar #1:Pattern puzzle<br />
    7. 7. Pick up to 2-3 design patterns to review next time<br />Question to audience<br />
    8. 8.
    9. 9. Best practices: Mylyn & Atlassian connectors(Mini Seminar #2)<br />Leonid M.<br />
    10. 10. Development process<br /><ul><li>Values & Principles: Brainstorming?
    11. 11. Practices: Brainstorming
    12. 12. ESWIJI project on the map</li></ul>Mylyn<br /><ul><li>Tying it all together (in context if ESWIJI project)</li></ul>Mini seminar #2: Agenda<br />
    13. 13. Brainstorming: Values?<br />
    14. 14. Brainstorming: Practices?<br />
    15. 15. ESWIJI project on the map<br /><ul><li>Use tools not brains
    16. 16. Easify & Delegate </li></li></ul><li>Mylyn<br />
    17. 17. Code change – is change request <br />- Mylyn enables task focused interface, coding against a task is a MUST<br />Bug tracking systems<br /><ul><li>Mylyn to “anything” connector (unified interface)</li></ul>Issue & document linking<br /><ul><li>Commit is linked against task
    18. 18. Task context is linked to the issue
    19. 19. Code comments are resolved to tasks</li></ul>Measures (worklog)<br />- “Real work” measures are provided <br />Traceability #1<br />
    20. 20. Traceability #2<br />
    21. 21. Traceability#3: Worklog<br />
    22. 22. Code views<br /><ul><li>Svn rev1:rev2 code review smells (actual state is in the scope of interests)
    23. 23. Reviewing SVN history is unnecessary effort
    24. 24. We want to see that was in mind (the whole context)
    25. 25. Isn’t the code review issue-oriented? </li></ul>Information & Expertise sharing#1 <br />
    26. 26. Information & Expertise sharing#2 <br />Why not to review Mylyn issue context instead?<br />
    27. 27. AIR & Bamboo<br />Build from your IDE<br />See build status<br />Navigate to the roots of the tests failure<br />
    28. 28. Gotohttp://www.infoq.com/presentations/mik-kersten-eclipse-mylin-tfi<br />Still not persuasive?<br />
    29. 29. Questions<br />

    ×