-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated README #963
updated README #963
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approval based on adding tweaks -- see my suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good -- some comments on contents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a few very small comments. Nice work!
README.md
Outdated
|
||
# Hamilton | ||
With Hamilton, write a directed acyclic graph (DAG) of data transformations using regular Python functions. You don't even need to `import hamilton`! It uses the function name and parameters to resolve the graph. As shown below, functions specify their dependencies, resulting in readable code that can always be visualized. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reiterate the tagline in the first sentence -- provides value
README.md
Outdated
|
||
from hamilton import driver | ||
- **Low-friction dev to prod**. Use `@config.when()` to modify your DAG between execution environments instead of error-prone `if/else` feature flags. The notebook extension prevents the pain of migrating code from a notebook to a Python module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Order is off -- put higher value ones first (effective collaboration + low-friction dev-to-prod)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had it this way because it enabled me to link in order:
- functions and nodes
- Driver definition
- function modifiers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think ordered linking is important -- we want to order it by clear attainable value IMO
Significant changes to README sections. Feel free to discuss things that should be:
Changes
How I tested this
Notes
Checklist