8 ms·

Those are called functions.

• Aeglaecia 2y ago
  imagine having the brain to synthesise every function across a codebase , most humans gotta settle for interfaces :p
  • minkles 2y ago
    Interfaces are just collections of function prototypes.
    • Aeglaecia 2y ago
      and some projects have more interfaces than are memorable by the average human
• jimbokun 2y ago
  Sometimes. Sometimes it is one or more programs writing to a queue or topic, and other programs reading from that topic. Or programs writing to and others reading from a Unix pipe. Or programs talking to each other using HTTP. Or Erlang processes communicating concurrently on one machine or across a network. Or different programs sharing one database. Or many objects communicating by passing messages in a small talk program. There are many ways to encapsulate programs and have them interact.
  • minkles 2y ago
    > Or programs writing to and others reading from a Unix pipe. write(message), read() -> message > Or programs talking to each other using HTTP. request() -> response > Or Erlang processes communicating concurrently on one machine or across a network. sendMess(message), waitMess() -> message > Or different programs sharing one database. execute(query) -> response ... I'm a mathematician at heart so I'm staying away from category theory as long as possible.
  • ellis0n 2y ago
    Totally agree and it depends on the current context of the programmer. For example, in the ACPUL language the program is split into boot images, files, modules, functions and expressions. All of these represent different levels of context encapsulation
  • wduquette 2y ago
    Or to put it another way…clean architecture is how you arrange the code so that you don’t need to keep ALL of it in your head at once, just the big picture and this bit here.
• jll29 2y ago
  The UNIX way would be to break things down into actual programs, where each one would be doing one thing well - and in such a way that they'd be useful as building blocks for solving other problems also.
  • minkles 2y ago
    The unix way is re-parsing text 5000 times in separate programmes with no consistency or contract between them really. That's not great.
    • jimbokun 2y ago
      Only great enough to be the operating system for the vast majority of computing devices on the planet.
      • tonyedgecombe 2y ago
        The world is full of technologies that are ubiquitous but imperfect.
        • jimbokun 2y ago
          https://en.wikipedia.org/wiki/Worse_is_better https://en.wikipedia.org/wiki/Worse_is_better
      • Too 2y ago
        In close competition with the well renowned JavaScript.
  • Too 2y ago
    This must not be done prematurely. Replacing function calls with processes quickly break “go to definition” and all the other conveniences or guardrails provided by your compiler toolchain. Unfortunately been dropped into that situation. The system was constantly broken due to missing of malformated arguments. Nobody dared to change anything. Same applies to prematurely microservicing a monolith. At least there folks seem to be sensible enough to use protobufs or json, instead of loosely typed strings.