5 Matching Annotations
  1. Jan 2025
    1. At the same time, it is the only environment today in which to learn and practice Moldable Development.

      Esto ya no es cierto. Sistemas como Clerk han adoptado explícitamente el término amoldable para describir la visión, citando a Tudor y su grupo.

      En Grafoscopio, nos hemos venido decantando por Sistemas Maleables, pues siento que describe mejor nuestra intención distinta no de "iniciar una conversación" (entre desarrolladores) como afirma Tudor, sino de enmarcarnos en una conversación más antigua, diversa y amplia, que por ejemplo recoge ideas de Maturana y Varela (autopoiesis), Freire (alfabetismos críticos), Kay (Dynabook), la comunidad de Pharo, la de GToolkit, Wenger (comunidades de prácticas) y las propias en diálogo con ellas (infraestructuras de bolsillo, computación convivial) etc.

    2. ndeed, as we can only perceive details related to a software system through tools, it follows that the tools are essential to the act of programming. At the same time, because software is highly contextual, for tools to be effective they also have to be contextual. The above examples are all quite different. In fact, each could be considered as a separate vertical in the software engineering tooling space. Yet, they were all expressed uniformly in the same environment. This shows that these tools are not distinct and that they can be combined and customized arbitrarily. There is just a fluid environment. We do not go to tools. Tools come to us. And we can make them come to us in our terms, in our context. That's the premise of Moldable Development.
  2. Jan 2023
    1. run on a wide variety of hardware - desktops, laptops, tablets, phones, watches

      Curious if he means can run on different devices or an installation spans multiple devices. I'm interested in considering the operating system as a control plane for many devices. Additionally multi-user support for sharing hardware.

  3. Aug 2022
    1. At 3 am he realized he needed to change the process scheduler. He read enough code to find the right method, changed it, and continued with his project

      How do we enable this while preventing people from accidentally nuking their systems?

    1. when you start with something simple but special purpose, it inevitably accretes features that attempt to increase its generality, as users run into its limitations. But the result of this evolutionary process is usually a complicated mess compared to what could be achieved by designing for generality up-front, in a more holistic way.

      I think this is true, but it's often difficult to design generality upfront. A nice approach is making sure that you are able to back into it and modify after the fact.

      We should be trying to make our technologies have more "two-door" decisions.