writing about some of the architectural challenges of making deeply flexible and extensible experimental frameworks I'm gonna be working on over here
RT @auto_pi_lot@twitter.com
after a number of rebuilds reflective of the challenge of hardware control on the raspi, we'll be clarifying the inheritance system to use backends as parallel mix-ins. rather than optimizing one system we'll work on making a clear path to define them
🐦🔗: https://twitter.com/auto_pi_lot/status/1478982008323801088
semantic wikis are powerful for communal development- creating multiple, mutually reinforcing means of interacting with a tool. combined with a plugin system (itself using the wiki), thinkin bout a different way of combining technical knowledge with code https://twitter.com/auto_pi_lot/status/1478987157058453505?t=ZTzF-7XnYPgSCwI-ThBakw&s=19
this thread a tiny tiny example of why this is hard to do and how architecture of a tool is not neutral to the kind of use patterns it supports. (the STS ppl will roast me for saying the obvious) https://twitter.com/auto_pi_lot/status/1478986353408811008?t=ZTzF-7XnYPgSCwI-ThBakw&s=19
particularly when the barriers to contributing code is much lower than a pull request. or even a specific code structure! like just fill out a form and take notes on a wiki Article and someone can find and use your stepper motor driver class!
idk I think it is cool and it has helped my work and have tried to make it easy to use but I could be wrong about literally everything and am always open to criticism.