iamsamwood

4 ms·

1. 1.▲
   by iamsamwood 9mo ago

   Those tools are excellent for simple data movement, but drag-and-drop becomes unwieldy as logic density increases. This often leads to script bloat, where developers embed code inside nodes, creating the worst of both worlds. We keep proces
2. 2.▲
   by iamsamwood 9mo ago

   Fair point on the terminology. We generally define a "mega-workflow" by the scale of the logic and participants involved—-typically processes spanning multiple teams, 10+ systems, and anywhere from 50 to thousands of individual ta
3. 3.▲
   by iamsamwood 9mo ago

   Debugging at scale is simplified architecturally by separating the integration/glue from the core process logic, where the platform handles that integration glue for you. This decision focuses all the debugging efforts on a single Comm
4. 4.▲
   Show HN: Luther Enterprise: Dev platform for operating end-to-end mega workflows(enterprise.luthersystems.com)

   8 points by iamsamwood 9mo ago|6 comments
5. 5.▲
   by iamsamwood 2y ago

   We've been using our own lisp dialect, ellipse ( https://github.com/luthersystems/elps ) for several years in exactly that domain and it's been our secret weapon.