Idée qui revient régulièrement:
Faire des petites choses très ciblées qui marchent isolées. Mises ensembles elles essaient de se coordonner dynamiquement en retombant sur leurs pattes (garder une cohérence quoiqu'il arrive). Leur comportement est explicite et modifiable par un observateur.
Rejoint des légos (qui peuvent être agencés suivant un modèle ou pas), les écosystèmes naturels, etc ...
Focus et contraintes:
tests, docs: force yourself to adopt a different point of view on your work to ensure its quality and adequation to reality
design / UX: can work only if you're dedicated to use it (in the same way that tests: you're confident you can blindly modify code, docs: anybody knew find your code cool and accessible). UX should be: it's gonna be smooth to use and direct to the point.
=> Talk about managing developers obsessions (factory boy, one liner, mr clean, etc ...) we've got a common one "how could I talk a computer into doing that" => make your obsessions a super power, not a weakness by recognizing it and where / when to express it.
One and only one complexity at a time => le reste est bien cadré (docs, tests, management) mais on a un espace de créativité, un défouloir où on est responsable.
Inspiré par le code: Communication
Commenting (expliciting) is great. Self-explanatory is even better (transparent) Faire
Don't talk just do...
... And just what you need to do (YAGNI) ...
... But before fake it till you make it
Context switching is a bitch
Steal patterns. It already exists waiting to be (re)discovered
One challenge at a time. 0 is boring, 2+ is exhausting.
Hacking / tinkering is the way to create. Methods come next for reproduction
What's a MVP ?
credits: https://webdesign.tutsplus.com/articles/how-to-work-with-mvps-minimum-viable-products--cms-28689?utm_source=questions_to_ask_as_a_new_designer_and_the_power_of_desire_lines&utm_medium=weekly-newsletter&utm_campaign=marvel-newsletter-2017-04-25&utm_term=2017-04-25
Idée qui revient régulièrement: Faire des petites choses très ciblées qui marchent isolées. Mises ensembles elles essaient de se coordonner dynamiquement en retombant sur leurs pattes (garder une cohérence quoiqu'il arrive). Leur comportement est explicite et modifiable par un observateur. Rejoint des légos (qui peuvent être agencés suivant un modèle ou pas), les écosystèmes naturels, etc ...
Focus et contraintes: tests, docs: force yourself to adopt a different point of view on your work to ensure its quality and adequation to reality design / UX: can work only if you're dedicated to use it (in the same way that tests: you're confident you can blindly modify code, docs: anybody knew find your code cool and accessible). UX should be: it's gonna be smooth to use and direct to the point. => Talk about managing developers obsessions (factory boy, one liner, mr clean, etc ...) we've got a common one "how could I talk a computer into doing that" => make your obsessions a super power, not a weakness by recognizing it and where / when to express it.
One and only one complexity at a time => le reste est bien cadré (docs, tests, management) mais on a un espace de créativité, un défouloir où on est responsable.