Skip to content
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

Write "The Pebete Way" #24

Open
jairot opened this issue Oct 30, 2013 · 2 comments
Open

Write "The Pebete Way" #24

jairot opened this issue Oct 30, 2013 · 2 comments

Comments

@jairot
Copy link
Contributor

jairot commented Oct 30, 2013

Writing a explicit declaration of design principles is a non trivial issue and i believe that should be done now that we have a clean repo.

Some sentences from the chat we had at the table:

"If we have to write a lot of code, we are doing something wrong"

"Everything should be plug in"

@felipelerena
Copy link

Maybe we can start with this:

Everything you do often in a python project should be a command
Everything should be a plugin
Command installing should be lazy and easy
All the commands should be easy to understand and to explain
If you have to read more than 2 lines of documentation to use a command the command is too complex
If a building tool from another language implements it and it's a good idea we should copy and invite the developers a beer
If a command is very popular it should be part of the default set
Let's use other people work so we can write less code and drink more wine

@marianoguerra
Copy link
Member

convention over configuration, but optional configuration

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

No branches or pull requests

3 participants