loman

Many modern tragic figures (e.g., Willy Loman in Death of a Salesman) are ordinary people, beaten down by everyday problems.

My team has been working on a Python library called Loman that represents computations as graphs.

He was the Willy Loman of the late 20th century.

The graph structure and visualization make it easy to return to loman graphs with up to low hundreds of nodes, which would make for a fearsome notebook otherwise.

Each node represents a part of the calculation and contains a value, similar to a cell in an spreadsheet, and Loman tracks what is stale as you update inputs.

The ease of the calculation tree in Excel versus having to keep track of what cells in a notebook you have updated was a large part of why we built and open-sourced Loman [1].

This is a challenge for me because I also felt the need to do the Willy Loman thing for a while but then realized that other people needed me to be more open about negative emotions or pessimism.

Our intention with Loman was to create a library scoped for a single process - we looked at the possibility of creating a system responsible for executing much larger graphs on a real-time ongoing basis, but it felt like a larger project than we'd be able to execute well.

It's because Americans think Willy Loman was the hero in "Death of a Salesman".

Loman explained, “This variant is strongly associated with where we are seeing increasing rates of covid-19.

Not every salesman is Willy Loman, and the insult you saw is solely in your mind.

The reads lengths might be fascinating with Nick Loman's group reporting upto an Mb in size.

My old team created a library called Loman, which we open-sourced, which uses DAGs to represent calculations.