User: dan@sartography.com clicked save for examples/1-basic-concepts/understanding-data-part-1/python.bpmn
This commit is contained in:
parent
ce5151a7d5
commit
07367447cd
|
@ -71,8 +71,27 @@ Avoid names that don't have meaning, or are cryptic. Try to names that are desc
|
|||
* x = "Abraham Lincoln" (NO)
|
||||
* fn = "Abraham" (NO)
|
||||
|
||||
EEE
|
||||
### Use blank lines, sparingly, to show clear steps
|
||||
A little white space can make your code more readable.
|
||||
So can comments.
|
||||
|
||||
### Use Comments
|
||||
A few carefully chosen words can help *IF it isn't apparent already.* Good variable names and well written code come first.
|
||||
|
||||
|
||||
|
||||
### Closing Brackets and braces
|
||||
We work with dictionaries a lot. So we recommend closing your braces and brackets with the first line to make it easy to tell when the dictionary definition is complete. For example:
|
||||
|
||||
|
||||
```python
|
||||
children = {
|
||||
"Robert",
|
||||
"Edward"
|
||||
"Tad",
|
||||
"Willie"
|
||||
}
|
||||
```
|
||||
</spiffworkflow:instructionsForEndUser>
|
||||
</bpmn:extensionElements>
|
||||
<bpmn:incoming>Flow_0ggy7w4</bpmn:incoming>
|
||||
|
|
Loading…
Reference in New Issue