| | 1 | = Minutes 2010/03/13 = |
| | 2 | |
| | 3 | * Talks on packaging tied will together - notes at TalkPackaging |
| | 4 | |
| | 5 | == Feedback from Python Training == |
| | 6 | |
| | 7 | First training course run last week |
| | 8 | |
| | 9 | * 5 people (6 registered, the maximum, but one pulled out) |
| | 10 | * Filled up really quickly - could easily run more courses |
| | 11 | * Feedback was pretty positive |
| | 12 | * Preparation could be better |
| | 13 | * Graeme and Simon spent 2-3 hours preparing |
| | 14 | * Simon wrote the examples - the idea was to alternate, Simon did a larger proportion though |
| | 15 | * This was designed as ''Python for Programmers'', but there was too much squeezed in, and so ran out of time |
| | 16 | * It was an interactive workshop, but got less so as time ran out |
| | 17 | * Mean to run from 11-3, but ran till 4 and still didn't cover anything |
| | 18 | * There wasn't really anything that could be easily taken out - more time is needed for a basic Python course |
| | 19 | * May help to cater to particular languages people already know in |
| | 20 | * It would probably help more to separate out courses for people with different skill levels |
| | 21 | * But it's difficult to assess skill levels before the course |
| | 22 | * Did a whole section on different numeric types - difficult to know what stuff people would need |
| | 23 | * Ways to improve: |
| | 24 | * A lot more detailed documentation would help - then people can branch into topics that suit them |
| | 25 | * Focused details - subset of most commonly used aspects rather than full coverage |
| | 26 | * Should probably be 2 4-hour sessions (consecutive Saturdays, or following days) |
| | 27 | * Having a week in between would help people to get to grips with the concepts from the first course |
| | 28 | * Finding good materials that people could use themselves in between could help |
