2. Overview
1. Performance. Definition and issues.
2. Who is low performer.
3. Who is high performer.
4. Secrets of top performer.
5. Four steps to become top performer.
6. Summary.
7. Resources.
3. Performance. Definition and issues
• Performance is a key metric of any successful
activity.
• Performance vs Quality is a goal of any
successful organization.
• Bad performance causes loosing of money,
projects, job, bad mood and decrease self-
estimation.
4. Who is low performer?
• Not a problem solver.
• Performs same task slower than other team
members.
• Misses meetings/deadlines/anything.
• Learns new things very slowly.
5. Who is high performer?
• Problem solver.
• Quick learner.
• Responsible and Result – Oriented.
• Researcher.
6. From low to high performer path
Q: Is it possible to grow top performer
from low performer?
7. Top Performer (revealed secrets)
• Great organizing and Time Management skills.
• Automating skills (know environment,
scripting, reporting technologies).
• Lazy in development (DRY, KISS principles).
• Great learning skills.
• Strong fundamental skills.(OOP, Algorithms).
8. Low performer -> High Performer
step 1
• Don’t waste a lot of time time on operational
activities (smoking, playing games etc).
• TODO lists.
Use planning tools.
OneNote, KeepNote
• Organize work with email.
9. Low performer -> High Performer
step 2
• Know your IDE and OS features.
• Automate you daily work (script languages,
job schedulers)
10. Low performer -> High Performer
step 2 - Automating tools
• IDE features (refactoring, simple code
generation).
• Tools for working with text.(sed, awk, grep).
Regular expressions.
• Build systems (make, ant, maven).
• UI automating tools (Selenium).
• Scripting languages (bash, ruby, perl, python).
11. Low performer -> High Performer –
step 2 - Demo
• Refactoring with eclipse IDE.
• Automate Web Navigation with Selenium.
12. Low performer -> High Performer
step 3
• Don’t reinvent the wheel.(use existing
external frameworks and internal modules,
reuse OOP principles).
• Check yourself. Make self-review and use
static analyzers of code.
• Be focused (use different views,
improved navigation with shortcuts)
13. Low performer -> High Performer
step 3 - DEMO
• FindBugs as static tool for analyze java code.
14. Low performer - High Performer
step 4
• Learning practices:
- Memory games and trainings.
- Mind Maps
- Use S3QR method as reading practice.
• Gathering ideas (use OneNote to copy&paste
main ideas from different books).
• Other methods
15. Summary
• Plan everything.
• Be lazy.
• Train yourself every day.
• Time is money. Don’t forget this.
16. Resources
• O’Relly Neal Ford “Productive Programmer”.
• Andy Hunt “Pragmatic Learning”.
• David Allen “Getting Things Done”.
