jonellalvi

Summary of Write the Docs:

A smattering of good stuff from the conf:

Day 1:

1. You won't know what you need to fix (in the docs) until you validate what you've written by having someone else read it
2. It takes a lot to break through to understanding (ex. Helen Kellar) but what we do to make sure we're communicating properly matters.
3. When testers and tech writers work together, you get a better end product because the tester is the voice of the customer when the customer isn't around.
4. Look back at past tickets--were they answered using a reference to a doc? could it be answered with a reference to an existing doc? add a link to the doc or create a doc for it if there isn't one.

jonellalvi

import datetime


class Timetable(object):
    '''
    Makes a timetable, which is a list of dates,
    based on data from the form (form_data)
    '''

jonellalvi

import datetime
# make this into a class
class Timetable(object):
    '''
    Makes a timetable, which is a list of dates,
    based on data from the form (form_data)
    '''

    def __init__(self):
        '''

jonellalvi

import calendar
import datetime
from datetime import timedelta


# set some sample data:
form_data = {
    'has_thursday': False,
    'name': u'Test',
    'color': u'green',

jonellalvi

# If you want to simply activate the virtualenv
echo 'alias PROJECT_NAME="source $HOME/programming/PROJECT_NAME/bin/activate" ' >> ~/.bash_aliases

# Or if you want to activate and also move to the directory:
echo 'alias PROJECT_NAME="source ~/programming/PROJECT_NAME/bin/activate; cd ~/programming/PROJECT_NAME" ' >> ~/.bash_aliases

# Don't forget this:
bash