Skip to content
This repository has been archived by the owner on Jan 10, 2019. It is now read-only.

Common paradigms and patterns should be encouraged more! #145

Open
mintsoft opened this issue Nov 8, 2014 · 3 comments
Open

Common paradigms and patterns should be encouraged more! #145

mintsoft opened this issue Nov 8, 2014 · 3 comments

Comments

@mintsoft
Copy link
Collaborator

mintsoft commented Nov 8, 2014

We're starting to build up a couple of nice work patterns around Goodies and Spices wrt to the "best way" to handle things; for example the NumberStyler and Dates role things.

I think it'd be nice if the docs show people what's available for reuse easily in a more focused way; currently I think users have to be hunting for them already to actually find them. Most people probably end up writing their own, do the PR and then get told "btw this just works, all your labour can be scrapped!"; which seems kinda wasteful.

What do others think? Some sort of "common practises" section?

Example: duckduckgo/zeroclickinfo-goodies#734 (comment)

@mwmiller @moollaza @jagtalon @mattr555

@moollaza
Copy link
Member

moollaza commented Nov 9, 2014

Yes! I agree, we can add it to the resources and add some mentions of it in the setup process - I'm currently working on a PR that reflows the intro to development and down the line there will be a larger redesign to the docs (which I can't wait for) because the very linear flow and the collapsed sidebar doesn't help to create awareness of what other pages/resources are available, which is a problem

@mattr555
Copy link
Collaborator

mattr555 commented Nov 9, 2014

We should totally have this. We already have the documentation on the DDG Namespace which has a lot of reusable functions, so I guess the idea is to make these resources more obvious throughout the tutorial and docs. Maybe like "Wait! Before you implement that common task, check to make sure it hasn't been done for you in the {perl roles,DDG namespace}!"

@mintsoft
Copy link
Collaborator Author

mintsoft commented Nov 9, 2014

Maybe like "Wait! Before you implement that common task, check to make sure it hasn't been done for you in the {perl roles,DDG namespace}!"

Exactly! I think better visibility is all that's needed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants