readme driven development

50
Readme Driven Development (and how to be a better writer) Mark Rickerby

Upload: mark-rickerby

Post on 05-Dec-2014

2.468 views

Category:

Technology


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Readme Driven Development

Readme Driven Development

(and how to be a better writer)

Mark Rickerby

Page 2: Readme Driven Development
Page 3: Readme Driven Development

UPPERCASETraditionally used to denotehuman readable !les

Page 4: Readme Driven Development

READMEINSTALLAUTHORSNEWS

FAQLICENSECHANGELOGTODO

Page 5: Readme Driven Development

Read me!A call to action

Page 6: Readme Driven Development

Traditional view:

Roadmap of a project

Page 7: Readme Driven Development

Traditional view:

Explain !le structure

Page 8: Readme Driven Development

Traditional view:

Write at the last minute

Page 9: Readme Driven Development
Page 10: Readme Driven Development
Page 11: Readme Driven Development

Modern view:

Statement of intent

Page 12: Readme Driven Development

Modern view:

Design document

Page 13: Readme Driven Development

Modern view:

Write your Readme !rst

Page 14: Readme Driven Development

“It rewards you for keeping libraries small and modularized” – Tom Preston Werner

Page 15: Readme Driven Development

www.antoniotahan.com

Mise en place

Page 16: Readme Driven Development

Introduction

One paragraph summary

Page 17: Readme Driven Development

Introduction

[W] is an [X] that does [Y] through [Z]

Page 18: Readme Driven Development

Getting Started

Explain the steps to install and link to further info

Page 19: Readme Driven Development

Getting Started

Show usage examples

Page 20: Readme Driven Development

Explore your API

Write from a user perspective

Page 21: Readme Driven Development

### POST Method

Call the `post()` method to make an HTTP post request:

```$http = new Net_Http();

$http->post($uri, $data);

if ($http->getStatus() == 201) $body = $http->getBody();```

Page 22: Readme Driven Development

### POST Method

Call the `post()` method to make an HTTP post request:

```$http = new Net_Http();

$response = $http->post($uri, $data);

if ($response->getStatus() == 201) $body = $response->getBody();```

Page 23: Readme Driven Development

Good style matters

Page 24: Readme Driven Development

Use Markdown

Or one of many alternatives

Page 25: Readme Driven Development

Sections as a guide

Introduction • Summary Installation • Downloads • FAQ

Getting Started • Examples Contributors

Page 26: Readme Driven Development

Structure

Limit headings toH2 & H3 only

Page 27: Readme Driven Development

Formatting

Use code to highlight keywords and examples

Page 28: Readme Driven Development

Punctuation

Use real quotation marks:“double” or ‘single’

Page 29: Readme Driven Development

PunctuationUse en dash correctly:

April–MaySydney–Melbourne

Bose–Einstein

Page 30: Readme Driven Development

PunctuationUse em dash correctly:

To break a thought—in a stronger way than using parentheses—an em dash

should be used.

Page 31: Readme Driven Development

Writing well

Page 32: Readme Driven Development

Information that is necessary for successful communication

Information thatis helpfulbut notcrucial

Nice toknow

Page 33: Readme Driven Development

Maintain coherent state

Don’t assume knowledge that doesn’t exist yet

Page 34: Readme Driven Development

Understand tone

Use the right language for the audience

Page 35: Readme Driven Development

https://github.com/play/play

“It’s true. It’s in a README.”

Page 37: Readme Driven Development

Eliminate repetition

Avoid using the same word or phrase over and over

Page 38: Readme Driven Development

Vary sentence structure

Helps reading "ow

Page 39: Readme Driven Development

Avoid the passive

“The chicken crossed the road.”vs

“The road was crossed by the chicken.”

Page 40: Readme Driven Development

“Never use a long word when a short

one will do”– George Orwell

Page 41: Readme Driven Development

Driving projects with

writing

Page 42: Readme Driven Development
Page 43: Readme Driven Development

Crowdfunding

Page 44: Readme Driven Development
Page 45: Readme Driven Development

A model for successful

collaboration?

Page 46: Readme Driven Development
Page 47: Readme Driven Development
Page 48: Readme Driven Development
Page 50: Readme Driven Development

Thank you.