Show
Ignore:
Timestamp:
04/12/07 17:38:04 (17 months ago)
Author:
Tarek Ziad?? <tarek@…>
Message:

rupy slides, starting up

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • PyCon07/slides.txt

    r76 r78  
    2222- Creator of AFPY (french speaking PUG) 
    2323 
    24 - CTO at Emencia, for a Python e-commerce framework   
     24- CTO at Emencia, for a Python e-commerce framework 
    2525 
    2626 
     
    3030- Understand the place of documentation in software projects 
    3131 
    32 - Learn a few patterns to document your project  
     32- Learn a few patterns to document your project 
    3333 
    3434- Practice them ! 
     
    3838 
    3939- Each part comes with: 
    40   
     40 
    4141 - a few slides 
    4242 - exercises *you* do. 
     
    5353- LUNCH - Yeeahhaa 
    5454 
    55 A few definitions  
     55A few definitions 
    5656================= 
    5757 
    5858What kind of documentation are we talking about ? 
    5959 
    60 A few definitions  
     60A few definitions 
    6161================= 
    6262 
    6363Technical documentation that helps to understand how a codebase 
    64 works and how it can be used.  
     64works and how it can be used. 
    6565 
    6666This can be: 
     
    7171- a recipe 
    7272 
    73 A few definitions  
     73A few definitions 
    7474================= 
    7575 
    7676What is the use and who is the target ? 
    7777 
    78 A few definitions  
     78A few definitions 
    7979================= 
    80   
     80 
    8181- Project developers, to... 
    8282 
     
    9999- Writing techniques ans tips: the seven laws 
    100100- Team writing 
    101   
     101 
    102102Mastering reSTructuredText 
    103103========================== 
     
    170170=================== 
    171171 
    172 Focus on your target when you write a document (RÃŒping, 2003).  
     172Focus on your target when you write a document (RÃŒping, 2003). 
    173173 
    174174Assume their background knowledge to restrict the scope of the documentation. 
     
    179179=================== 
    180180 
    181 A document is about a clear focus.  
    182  
    183 A precise title for each section and the document itself, and a summary  
     181A document is about a clear focus. 
     182 
     183A precise title for each section and the document itself, and a summary 
    184184can help. 
    185185 
    186 |important| If you cannot easily name the document or one of its section,  
     186|important| If you cannot easily name the document or one of its section, 
    187187there's a problem 
    188188 
     
    197197    >>> foo = graph.calculateSquare(1, 1, 1, 1) 
    198198    >>> bar = graph.renderSquare(foo) 
    199     
    200 Better::  
     199 
     200Better:: 
    201201 
    202202    >>> from package import graph 
     
    208208 
    209209A working software is more important than the best documentation in the world 
    210 (Ambler, 2002).  
     210(Ambler, 2002). 
    211211 
    212212*Quality over Quantity* is the best rule. 
    213213 
    214 |important| Spending too much time to find something in the documentation is  
     214|important| Spending too much time to find something in the documentation is 
    215215a bad sign. 
    216216 
    217 |important| Think documents like code. Always limit the size of its sections,  
     217|important| Think documents like code. Always limit the size of its sections, 
    218218examples, etc. 
    219219 
     
    229229- a toc when there are more than one section 
    230230- references 
    231 - glossary  
     231- glossary 
    232232- tables and diagrams 
    233233 
     
    249249|important| The best pair is made with the end-user 
    250250 
    251 |important| Each document should have a champion, though.  
     251|important| Each document should have a champion, though. 
    252252 
    253253Team writing 
     
    260260    - cooking recipe 
    261261    - how to play a board or card game 
    262     - how to fish shrimps  
    263   
     262    - how to fish shrimps 
     263 
    264264 
    265265Writing a document 
     
    292292   :height: 350 
    293293   :width: 250 
    294   
     294 
    295295   Developer that write documentation (=winner) 
    296296 
     
    317317The code is documented with: 
    318318 
    319 - inline comments  
     319- inline comments 
    320320- functions, classes and modules docstrings 
    321321 
     
    346346- The text file describes what the module does 
    347347 
    348 - example: utils.txt and utils.py  
    349  
    350 - Let's practice: exercise #5 |glasses|  
     348- example: utils.txt and utils.py 
     349 
     350- Let's practice: exercise #5 |glasses| 
    351351 
    352352 
     
    360360- **CHANGELOG**: Lists of changes for each version of the package 
    361361- **INSTALL.txt**: how to install the package 
    362 - **TODO.txt**: Lists all things to do (sometimes replaced with a  
     362- **TODO.txt**: Lists all things to do (sometimes replaced with a 
    363363  link to a tracker or a website in README.txt) 
    364364 
     
    464464 
    465465- There's 3 level of documentation: 
    466    
     466 
    467467  - inline comments 
    468468  - docstrings 
    469469  - separated docstrings 
    470470- Packages comes with mandatory documentation 
    471 - We can do TDD with doctests, and deal with doc. like code  
     471- We can do TDD with doctests, and deal with doc. like code 
    472472 
    473473Pause 
     
    532532 
    533533- title & abstract (two sentences max) 
    534 - prerequest: level needed, other documents to read   
     534- prerequest: level needed, other documents to read 
    535535- toc (when # sections > 1) 
    536536- body 
     
    551551- A recipe answer to one question, that should be its title. 
    552552 
    553 - Each question is linked to the sentences founded in tutorials.  
     553- Each question is linked to the sentences founded in tutorials. 
    554554 
    555555- A recipe is short (2 screens) 
     
    561561 
    562562- How to code a RSS view ? 
    563 - How to extract the content of a web page ?  
     563- How to extract the content of a web page ? 
    564564 
    565565Recipes 
     
    569569 
    570570- title & abstract (two sentences max) 
    571 - prerequest: level needed, other documents to read   
     571- prerequest: level needed, other documents to read 
    572572- toc (when # sections > 1) 
    573573- body 
     
    587587- ..avoid using two terms for the same definition 
    588588- ..removes approximacies in documents: 
    589     not sure on how to explain a concept with simple words ?  
     589    not sure on how to explain a concept with simple words ? 
    590590    look in the glossary |wink| 
    591591 
     
    639639- It is enjoyed by most developers 
    640640 
    641 - It increases both writing and programming skills  
     641- It increases both writing and programming skills 
    642642 
    643643The end