(hidden) Nq8r6-ap2

words:	0 + 241 = 241
last update:

Linked Mentions (1 in 1 page)

i just re-discovered conway's law (public) (1)
- unless, ofc, the program would be completely extensible, meaning it would provide APIs to extend the behavior without modifying the program itself (O in [[(hidden) Nq8r6-ap2]] - open-closed)
  - https://en.wikipedia.org/wiki/Open%E2%80%93closed_principle
  - but then, the program becomes much more complex, with all the stuff that comes from that! and remember, what we tried turning into packages were actually small utilities/scripts - they didn't have any of the problems - the problems come from wanting to abstract those small utilities into packages
    - the convenience of consumption, at the loss of simplicity of modification
      - what can be learnt from this is that maybe one should never create an #[[(hidden) vzIV5rsdR]] (both 1) a utility function on some "reusable logic" and 2) a library/framework instead of a template) on top of some logic __without__ first using it enough to realize the common use cases to identify the things that can and __should__ be abstracted, and only then start abstracting.
        
        because in some cases nothing should be abstracted - then the choice is having a template instead of a library, or copy-pasted / #[[(hidden) imNiDHw0b]] (as opposed to #[[(hidden) AYIfX5dlb]]) code
        
        and sometimes very little things need to be abstracted - then we can create & extract more sophisticated & extendable programs but keep everything else as a template.
        
        ((G5zfo90eS))
        
        yet again [[react]]'s philosophy checks out - abstract the most important bits, and let the community grow & develop everything else. eventually, if things mature enough, we come back to:
        
        ((qCxgd284G))